dbcve.org
Application Policy Infrastructure ControllerApplication · Cisco

CVE-2019-1692

MEDIUM · 5.3 CVSS v3.1 Published 2019-05-03
Fix available
A fix is available. Upgrade to 4.1 or later.
See remediation →
62/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
A vulnerability in the web-based management interface of Cisco Application Policy Infrastructure Controller (APIC) Software could allow an unauthenticated, remote attacker to access sensitive system usage information. The vulnerability is due to a lack of proper data protection mechanisms for certain components in the underlying Application Centric Infrastructure (ACI). An attacker could exploit this vulnerability by attempting to observe certain network traffic when accessing the APIC. A successful exploit could allow the attacker to access and collect certain tracking data and usage statistics on an affected device.

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 · moderate confidence

Information disclosure vulnerability in Cisco APIC web-based management interface. Due to insufficient data protection mechanisms in the ACI components, an unauthenticated remote attacker can observe network traffic to collect sensitive system usage statistics and tracking data.

MitigationApply Cisco's official patch for this vulnerability. Until then, restrict network access to the APIC management interface using network segmentation and firewall rules to limit exposure to untrusted networks.

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
Application Policy Infrastructure ControllerApplication
Affected:< 4.1\(1i\)= 8.3\(1\)s6

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
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 checks

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

  1. Identify the APIC controller version
    Log into the APIC CLI via console or SSH and run the command 'show version' or access the APIC web interface and check the Dashboard for the firmware version. Note the exact version string.
    Affected if The installed version is lower than 4.1(1i) or exactly 8.3(1)s6.
  2. Determine if the APIC web management interface is network-accessible
    From an external network perspective, attempt to reach the APIC management IP on ports 80/443 (HTTP/HTTPS). Check firewall rules and access lists that govern access to the APIC management network.
    Affected if The APIC web interface is reachable from untrusted or external networks without proper network segmentation.
  3. Verify management traffic encryption
    Check whether the APIC web interface is served over HTTPS only. Attempt an HTTP request to port 80 and observe if it redirects to HTTPS or is blocked. Review SSL/TLS configuration on the APIC.
    Affected if The management interface allows unencrypted HTTP access or uses weak encryption, exposing traffic to interception.
  4. Assess network exposure of ACI leaf/spine switches
    Review the network topology and access controls for ACI leaf and spine switches that communicate with the APIC. Check if their management interfaces share the same network segment as the APIC.
    Affected if ACI components (leaf/spine) management traffic traverses networks accessible to untrusted users, allowing traffic observation.

The environment is affected if the Cisco APIC version is below 4.1(1i) or exactly 8.3(1)s6 AND the web-based management interface is accessible from networks where an unauthenticated attacker could intercept network traffic.

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
Upgrade available Upgrade to 4.1 or later
Fixed in 4.1
Interim mitigation

Apply Cisco's official patch for this vulnerability. Until then, restrict network access to the APIC management interface using network segmentation and firewall rules to limit exposure to untrusted networks.

Fix this in Application Policy Infrastructure Controller Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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