CVE-2005-3101
First published: Wed Sep 28 2005(Updated: )
The password reset feature in Movable Type before 3.2 generates different error messages depending on whether a user exists or not, which allows remote attackers to determine valid usernames.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Movable Type | =3.17 |
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-2005-3101?
CVE-2005-3101 is considered a medium severity vulnerability due to information exposure.
How do I fix CVE-2005-3101?
To fix CVE-2005-3101, upgrade Movable Type to version 3.2 or later to eliminate the differing error messages.
What impact does CVE-2005-3101 have on users?
CVE-2005-3101 allows attackers to determine valid usernames, which can lead to targeted attacks on these accounts.
Which versions of Movable Type are affected by CVE-2005-3101?
Movable Type versions prior to 3.2, including version 3.17, are affected by CVE-2005-3101.
Who can exploit CVE-2005-3101?
Remote attackers can exploit CVE-2005-3101 to identify valid usernames through the password reset feature.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/last-modified-date
- agent/references
- agent/author
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/six apart
- canonical/movable type
- version/movable type/3.17