CVE-2017-12223
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 · uneditedA vulnerability in the ROM Monitor (ROMMON) code of Cisco IR800 Integrated Services Router Software could allow an unauthenticated, local attacker to boot an unsigned Hypervisor on an affected device and compromise the integrity of the system. The vulnerability is due to insufficient sanitization of user input. An attacker who can access an affected router via the console could exploit this vulnerability by entering ROMMON mode and modifying ROMMON variables. A successful exploit could allow the attacker to execute arbitrary code and install a malicious version of Hypervisor firmware on an affected device. Cisco Bug IDs: CSCvb44027.
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 confidenceA vulnerability in the ROM Monitor (ROMMON) firmware of Cisco IR800 Integrated Services Routers allows an unauthenticated attacker with console access to modify ROMMON variables and boot an unsigned Hypervisor. This enables arbitrary code execution and installation of malicious firmware, compromising system integrity. The root cause is insufficient input sanitization in ROMMON.
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 dataall versionsCVSS 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
- Physical
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:H/PR:N/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 device modelConnect to the device console or use 'show version' command to confirm the hardware model is Cisco IR800 Integrated Services RouterAffected if The device model is Cisco IR800 series router
-
Check for console access exposureReview physical security controls and network access lists to determine if console/Telnet/SSH access to the device is accessible to unauthorized usersAffected if Console port is physically accessible or network-based console access is exposed without proper authentication controls
-
Inspect ROMMON variablesDuring device boot, press the ROMMON break key (typically Ctrl+Break or Ctrl+C) to enter ROMMON mode, then use 'set' or 'env' command to list current ROMMON environment variablesAffected if ROMMON can be entered without authentication and variables can be modified freely
-
Verify hypervisor boot configurationIn ROMMON mode, check boot variables using 'set' command to see if 'BOOT' or 'hypervisor' variables point to unsigned or modified image filesAffected if Boot variables reference unsigned images or show unexpected values indicating modification
-
Check for unexpected firmware imagesUse 'show flash' or 'dir flash:' command to list all firmware/hypervisor images stored on the device filesystemAffected if Unknown or unsigned firmware images are present in flash memory that were not installed by administrators
A Cisco IR800 router with accessible console ports where ROMMON can be entered without authentication and boot variables can be modified is affected by this vulnerability.
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 dataRestrict physical and console access to affected devices. Apply Cisco firmware updates when available. Monitor for unauthorized ROMMON access attempts.
- 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-2017-12223 — 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-2017-12223 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