dbcve.org
Application Policy Infrastructure Controller Enterprise ModulePlugin / extension · Cisco

CVE-2016-1318

MEDIUM · 6.1 CVSS v3.0 Published 2016-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site scripting (XSS) vulnerability in Cisco Application Policy Infrastructure Controller Enterprise Module (APIC-EM) 1.1 allows remote attackers to inject arbitrary web script or HTML via crafted markup data, aka Bug ID CSCux15489.

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

Cross-site scripting (XSS) vulnerability in Cisco APIC-EM version 1.1 allows remote attackers to inject arbitrary web script or HTML via crafted markup data. The vulnerability stems from improper sanitization of user-supplied markup input rendered in the web interface, enabling malicious scripts to execute in the context of other users' sessions.

MitigationApply vendor-supplied patches for APIC-EM 1.1 (Bug ID CSCux15489). Until patched, implement output encoding and input validation for all user-generated content displayed in the web interface to mitigate XSS risk.

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 Controller Enterprise ModulePlugin / extension
Affected:= 1.1_base

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Confirm Cisco APIC-EM is installed
    Identify if the Cisco Application Policy Infrastructure Controller Enterprise Module is deployed in your environment. This is typically a physical or virtual appliance. Check for the presence of APIC-EM services, processes, or known installation directories.
    Affected if APIC-EM is not installed in your environment, you are not affected.
  2. Check the installed APIC-EM version
    Access the APIC-EM web interface or API and retrieve the software version. Typically this is available via the login page, in the admin settings, or by querying the API endpoint for version information. Compare the version to the affected range: = 1.1_base.
    Affected if Your installed version is exactly 1.1_base, you are likely affected. Versions other than 1.1_base are not in the affected range.
  3. Verify the web interface is enabled and accessible
    Confirm that the APIC-EM web interface (GUI) is enabled and reachable. This is typically accessed over HTTPS on port 443. Check if the service is listening and responding.
    Affected if The web interface is disabled or not accessible, the XSS vulnerability cannot be exploited.
  4. Check for user-supplied input being rendered in the web interface
    Examine the web application to determine if user-generated content or markup input is displayed in the interface. This includes fields where users can enter text that gets rendered back to other users, such as device names, descriptions, or comments.
    Affected if User-supplied markup input is rendered in the web interface without proper sanitization, the XSS vulnerability is present.

You are affected if Cisco APIC-EM version 1.1_base is installed and its web interface is accessible, with user-supplied content being rendered without sanitization.

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 vendor-supplied patches for APIC-EM 1.1 (Bug ID CSCux15489). Until patched, implement output encoding and input validation for all user-generated content displayed in the web interface to mitigate XSS risk.

Fix this in Application Policy Infrastructure Controller Enterprise Module Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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