dbcve.org
HordeApplication · Debian

CVE-2009-0932

MEDIUM · 6.4 CVSS v2.0 Published 2009-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Directory traversal vulnerability in framework/Image/Image.php in Horde before 3.2.4 and 3.3.3 and Horde Groupware before 1.1.5 allows remote attackers to include and execute arbitrary local files via directory traversal sequences in the Horde_Image driver name.

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 confidence

Directory traversal vulnerability in Horde framework's Image.php allows remote attackers to include and execute arbitrary local files by supplying directory traversal sequences (e.g., ../../../etc/passwd) in the Horde_Image driver name parameter. The vulnerability stems from insufficient input validation on the driver name before using it in file inclusion operations.

MitigationUpgrade to Horde 3.2.4/3.3.3 or Horde Groupware 1.1.5 or later, which contain patched versions of Image.php with proper input sanitization. If immediate patching is not possible, implement input validation to reject directory traversal sequences in the driver name parameter.

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
HordeApplication
Affected:= 3.2= 3.2.2= 3.2.3= 3.3= 3.3.1= 3.3.2
Horde GroupwareApplication
Affected:= 1.1.1= 1.1.2= 1.1.3= 1.1.4

CVSS 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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Horde version
    Locate the Horde installation and check its version number, typically found in a version file or in the main Horde directory (e.g., lib/Horde.php, composer.json, or a VERSION file). Compare against the affected versions: Horde 3.2 through 3.3.2 or Horde Groupware 1.1.1 through 1.1.4.
    Affected if The installed version is exactly 3.2, 3.2.2, 3.2.3, 3.3, 3.3.1, 3.3.2 (for Horde) or 1.1.1, 1.1.2, 1.1.3, 1.1.4 (for Horde Groupware).
  2. Locate the vulnerable Image.php file
    Find the Image.php file within the Horde framework installation, typically under the library path such as lib/Horde/Image.php or horde/lib/Horde/Image.php.
    Affected if The Image.php file exists and is present in the Horde installation directory.
  3. Check if Horde_Image driver parameter accepts external input
    Inspect the Image.php source code and look for how the driver name parameter is handled. Search for include, require, or similar file inclusion statements that use the driver name without proper validation.
    Affected if The code uses the driver name parameter directly in file inclusion operations (include/require) without sanitizing directory traversal sequences like ../..
  4. Verify web server access to the Image.php script
    Determine if the Image.php file is accessible via the web server. Check the web server configuration and Horde's routing to see if Image.php can be invoked directly through HTTP requests.
    Affected if The Image.php script is accessible via web (not restricted by authentication or .htaccess rules), allowing an attacker to supply a driver name parameter.

You are affected if you run Horde 3.2-3.3.2 or Horde Groupware 1.1.1-1.1.4, the Image.php file exists with vulnerable code that uses the driver parameter in file inclusion without filtering ../ sequences, and the script is web-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Horde 3.2.4/3.3.3 or Horde Groupware 1.1.5 or later, which contain patched versions of Image.php with proper input sanitization. If immediate patching is not possible, implement input validation to reject directory traversal sequences in the driver name parameter.

Fix this in Horde Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-0932 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-0932 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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