CVE-2012-6609
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 · uneditedDirectory traversal vulnerability in a_getlog.cgi in Polycom HDX Video End Points before 3.0.4 and UC APL before 2.7.1.J allows remote attackers to read arbitrary files via a .. (dot dot) in the name parameter.
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 confidenceDirectory traversal vulnerability in Polycom HDX Video End Points and UC APL allows remote attackers to read arbitrary files via '..' sequences in the name parameter of the a_getlog.cgi script. The vulnerability is exploitable without authentication due to insufficient input validation.
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< 3.0.4< 2.7.1.jCVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 the Polycom device modelAccess the web admin interface or check the device label to confirm whether it is a Polycom HDX Video End Point or Polycom UC APL system.Affected if The device is a Polycom HDX Video End Point or Polycom UC APL unit.
-
Check the firmware version on Polycom HDXLog into the HDX web interface and navigate to System Information or Admin Settings to view the firmware version. Compare it to 3.0.4.Affected if The installed firmware version is below 3.0.4.
-
Check the software version on Polycom UC APLLog into the UC APL admin console or check the system information page to view the software version. Compare it to 2.7.1.J.Affected if The installed software version is below 2.7.1.J.
-
Verify web interface accessibilityAttempt to access the HTTP/HTTPS management interface of the device from the network. The vulnerability is exploitable without authentication, so any exposed web interface is relevant.Affected if The web admin interface is reachable from the network without authentication.
-
Confirm a_getlog.cgi endpoint existsRequest the URL pattern 'http://[device-ip]/a_getlog.cgi' via HTTP GET to see if the script responds. A 404 indicates the endpoint may not exist or has been patched.Affected if The a_getlog.cgi script responds to requests (non-404 response), indicating the vulnerable endpoint is present.
The environment is affected if the device is a Polycom HDX Video End Point running firmware below 3.0.4, or a Polycom UC APL running software below 2.7.1.J, and the web management interface with the a_getlog.cgi endpoint is accessible.
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 data2.7.1.j3.0.4
Upgrade Polycom HDX Video End Points to firmware version 3.0.4 or later, and UC APL to version 2.7.1.J or later. If immediate patching is not possible, consider network segmentation to limit exposure of the video endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-6609 — 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-2012-6609 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