CVE-2002-2024
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHorde IMP 2.2.7 allows remote attackers to obtain the full web root pathname via an HTTP request for (1) poppassd.php3, (2) login.php3?reason=chpass2, (3) spelling.php3, and (4) ldap.search.php3?ldap_serv=nonsense which leaks the information in error messages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHorde IMP 2.2.7 contains a path disclosure vulnerability where multiple PHP scripts (poppassd.php3, login.php3, spelling.php3, and ldap.search.php3) leak the full web server root pathname in error messages, allowing remote attackers to obtain sensitive filesystem path information.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.2.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Horde IMP versionCheck the version.php or package version file in the Horde IMP installation directory, or look for version information in the IMP login page footerAffected if The installed version is exactly 2.2.7
-
Locate vulnerable PHP scriptsSearch for the files poppassd.php3, login.php3, spelling.php3, and ldap.search.php3 in the web server document root under the IMP or horde directoryAffected if Any of these four files exist in the Horde IMP installation
-
Verify PHP error display is enabledCheck the PHP configuration file (php.ini) for display_errors = On or check if error reporting is set to show all errors (E_ALL)Affected if PHP display_errors is enabled or detailed error reporting is active
-
Test for path disclosure in error messagesTrigger an error condition in one of the vulnerable scripts (e.g., request poppassd.php3 with malformed input or missing required parameters) and observe the error outputAffected if Error messages reveal the full filesystem path such as /var/www or C:\inetpub
-
Check web server access logsReview web server error logs for recent requests to the vulnerable scripts and examine any logged path informationAffected if Logged errors from these scripts contain full filesystem paths
You are affected if Horde IMP version 2.2.7 is installed and any of the vulnerable PHP scripts (poppassd.php3, login.php3, spelling.php3, ldap.search.php3) are present with PHP error display enabled or path information appearing in error logs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable detailed PHP error messages or upgrade to a patched version of Horde IMP that properly handles error conditions without exposing filesystem paths.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2002-2024 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data