dbcve.org
IoxApplication · Cisco

CVE-2016-9199

MEDIUM · 6.5 CVSS v3.0 Published 2016-12-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
A vulnerability in the Cisco application-hosting framework (CAF) of Cisco IOx could allow an authenticated, remote attacker to read arbitrary files on a targeted system. Affected Products: This vulnerability affects specific releases of the Cisco IOx subsystem of Cisco IOS and IOS XE Software. More Information: CSCvb23331. Known Affected Releases: 15.2(6.0.57i)E CAF-1.1.0.0.

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

An authenticated, remote attacker can read arbitrary files on the targeted system through the Cisco application-hosting framework (CAF) in Cisco IOx. This is a file disclosure vulnerability in the CAF component that allows authenticated users to access files outside the intended directory scope.

MitigationApply the Cisco patch for this vulnerability (refer to CSCvb23331) to the affected Cisco IOS/IOS XE software releases. If patching is delayed, restrict network access to IOx management interfaces and enforce strict authentication controls.

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
IoxApplication
Affected:= 1.1.0

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
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

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

  1. Identify if Cisco IOx is installed
    Check the system for Cisco IOx installation and determine the installed version. This may be visible in the IOS/IOS XE software show commands, IOx status displays, or system inventory listings.
    Affected if The system has Cisco IOx version 1.1.0 installed and the CAF component is present.
  2. Verify the IOx version number
    Locate the specific version identifier for the installed Cisco IOx instance. Compare this version against the affected range of version 1.1.0.
    Affected if The installed IOx version is exactly 1.1.0.
  3. Confirm CAF component is enabled
    Determine whether the Cisco application-hosting framework (CAF) is active or enabled on the system. This may be observable through IOx service status or configuration listings.
    Affected if CAF is enabled and accessible as part of the IOx deployment.
  4. Check IOx management interface accessibility
    Identify whether IOx management interfaces are exposed to network access. This includes evaluating interface bindings, ACLs, or management network configurations.
    Affected if IOx management interfaces are reachable from network locations where untrusted users could authenticate.
  5. Assess authentication configuration for IOx
    Review the authentication mechanisms configured for IOx and CAF access. Determine if local accounts, AAA, or other auth methods are properly enforced.
    Affected if Authentication controls are weak, default, or bypassed for CAF access.

A system is affected if it runs Cisco IOx version 1.1.0 with the CAF component enabled and accessible, particularly if IOx management interfaces are network-reachable without strict authentication enforcement.

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

Apply the Cisco patch for this vulnerability (refer to CSCvb23331) to the affected Cisco IOS/IOS XE software releases. If patching is delayed, restrict network access to IOx management interfaces and enforce strict authentication controls.

Fix this in Iox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-9199 — 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-2016-9199 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