Application Policy Infrastructure Controller Enterprise ModulePlugin / extension · Cisco
CVE-2016-1365
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 · uneditedThe Grapevine update process in Cisco Application Policy Infrastructure Controller Enterprise Module (APIC-EM) 1.0 allows remote authenticated users to execute arbitrary commands as root via a crafted upgrade parameter, aka Bug ID CSCux15507.
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 confidenceCommand injection vulnerability in the Grapevine update process of Cisco APIC-EM 1.0 allows remote authenticated users to execute arbitrary OS commands with root privileges by submitting crafted upgrade parameters. This stems from insufficient input validation in the upgrade functionality.
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
= 1.0.10CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Cisco APIC-EM versionAccess the APIC-EM controller administrative interface or use the CLI command 'show version' to retrieve the software version. In the GUI, navigate to the About or System Information page.Affected if The installed version is exactly 1.0.10 (version 1.0.10)
-
Confirm the Grapevine update component is presentCheck if the Grapevine update service is running on the APIC-EM instance. This may be visible in the system services list or process list accessible via administrative commands.Affected if The Grapevine update service is installed and running on the system
-
Determine if the upgrade/update endpoint is exposedReview the network configuration and access controls for the APIC-EM to identify if the upgrade functionality is network-accessible. Check for exposed HTTP/HTTPS endpoints related to updates or upgrades.Affected if The upgrade endpoint is accessible over the network to authenticated users
-
Verify if remote authenticated access is possibleReview user accounts and authentication settings to determine if remote authenticated users exist who could access the upgrade functionality.Affected if Remote authenticated users can access the APIC-EM system
You are affected if your Cisco APIC-EM installation is version 1.0.10, the Grapevine update service is active, and the upgrade endpoint is accessible to remote authenticated users.
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 a patched version of Cisco APIC-EM. Restrict access to the update functionality to trusted administrators only. If immediate patching is not possible, consider network segmentation to limit exposure to authenticated attackers.
Fix this in Application Policy Infrastructure Controller Enterprise Module
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1365 — 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-2016-1365 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