CVE-2002-2175
First published: Tue Dec 31 2002(Updated: )
phpSquidPass before 0.2 uses an incomplete regular expression to find a matching username in its database, which allows remote authenticated attackers to effectively delete other usernames via a short username that matches the end of the targeted username.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Php Phpsquidpass |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2002-2175?
CVE-2002-2175 is considered a moderate severity vulnerability due to its potential to allow remote authenticated attackers to manipulate usernames.
How do I fix CVE-2002-2175?
To fix CVE-2002-2175, upgrade to a version of phpSquidPass that is 0.2 or later, where the regular expression issue has been resolved.
What type of vulnerability is CVE-2002-2175?
CVE-2002-2175 is a security vulnerability that involves improper user authentication due to a flawed regular expression.
Who is affected by CVE-2002-2175?
Users of phpSquidPass versions prior to 0.2 are affected by CVE-2002-2175 and should take immediate action to prevent exploitation.
What impact does CVE-2002-2175 have on security?
CVE-2002-2175 can lead to unauthorized deletion of usernames, potentially disrupting user access and compromising account integrity.
- collector/nvd-historical
- collector/nvd-index
- agent/references
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/remedy
- agent/tags
- agent/description
- agent/event
- agent/source
- vendor/php
- canonical/php phpsquidpass