CVE-2015-2860
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 Avigilon Control Center (ACC) 4 before 4.12.0.54 and 5 before 5.4.2.22 allows remote attackers to read arbitrary files via a crafted help/ URL.
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 Avigilon Control Center allows remote attackers to read arbitrary files by crafting malicious help/ URLs with path traversal sequences (e.g., ../../). The vulnerability exists in ACC versions 4 before 4.12.0.54 and 5 before 5.4.2.22.
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<= 5.4.2.21<= 4.12.0.53CVSS 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
- Complete
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/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 installed Avigilon Control Center versionCheck the ACC server application version through the ACC Client (Help > About) or the ACC Server installation. The version number is typically visible in the software UI, installation logs, or Windows Programs and Features.Affected if Version 4.x is at or below 4.12.0.53, or version 5.x is at or below 5.4.2.21
-
Confirm the software edition (version 4 or version 5)Distinguish between ACC version 4 and version 5, as they have different patched version thresholds. The major version number appears in the About dialog and installation path.Affected if Running ACC version 4 before 4.12.0.54 or version 5 before 5.4.2.22
-
Verify if the ACC web interface or help feature is accessibleTest network accessibility of the ACC management interface ports (default HTTP/HTTPS ports). Attempt to reach the help endpoint by browsing to the ACC server URL with /help or similar paths.Affected if The ACC management interface is reachable over the network and the help feature is exposed
-
Check for evidence of exploitation attempts in logsReview ACC server logs for unusual requests containing path traversal sequences (../) targeting the help functionality, particularly looking for attempts to access files outside the help directory.Affected if Log entries show malformed help/ URL requests with ../ sequences
A user is affected if Avigilon Control Center version 4 is at or below 4.12.0.53 (or version 5 at or below 5.4.2.21) AND the ACC help feature or management interface is network-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 dataUpgrade to ACC version 4.12.0.54 or later for version 4, or 5.4.2.22 or later for version 5. If immediate upgrade is not possible, restrict network access to the ACC management interface and disable the help feature if not required.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2860 — 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-2015-2860 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