Unified Computing SystemApplication · Cisco
CVE-2019-1863
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 web-based management interface of Cisco Integrated Management Controller (IMC) Software could allow an authenticated, remote attacker to make unauthorized changes to the system configuration. The vulnerability is due to insufficient authorization enforcement. An attacker could exploit this vulnerability by sending a crafted HTTP request to the affected software. A successful exploit could allow a user with read-only privileges to change critical system configurations using administrator privileges.
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 confidenceIn Cisco IMC Software, the web-based management interface fails to properly enforce authorization checks, allowing authenticated users with read-only privileges to bypass permission boundaries by sending crafted HTTP requests. This enables unauthorized modification of system configurations that should require administrator-level access.
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
Unified Computing SystemApplication
= 4.0\(1c\)hs3
Integrated Management Controller SupervisorApplication
>= 1.5.0.0, < 1.5\(9g\)>= 2.0.0.0, < 2.0\(13o\)>= 3.0.0.0, < 3.0\(4k\)>= 4.0.0.0, < 4.0\(4b\)>= 4.0.0.0, < 4.0\(1d\)>= 4.0.0.0, < 4.0\(2c\)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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 Cisco IMC Software versionAccess the Cisco IMC web interface or CLI and retrieve the firmware/software version information. This is typically found in the firmware or version section of the management interface.Affected if The installed version matches one of the affected version ranges: 4.0(1c)hs3, 1.5.0.0 through 1.5(9g), 2.0.0.0 through 2.0(13o), 3.0.0.0 through 3.0(4k), 4.0.0.0 through 4.0(4b), 4.0.0.0 through 4.0(1d), or 4.0.0.0 through 4.0(2c).
-
Confirm the web-based management interface is enabledVerify that the Cisco IMC web-based management interface is active and accessible. Check the management interface settings to confirm HTTP/HTTPS web UI is turned on.Affected if The web-based management interface is enabled and reachable.
-
Check for existing user accounts with read-only privilegesReview the user account configuration in Cisco IMC to identify accounts that have read-only or non-administrative roles assigned.Affected if There are one or more user accounts configured with read-only or limited privileges.
-
Review audit logs for suspicious HTTP activityExamine the Cisco IMC audit or event logs for HTTP requests that may indicate a read-only user attempting to modify configurations that should require elevated privileges.Affected if Logs show read-only users performing configuration changes or accessing administrative functions.
You are affected if your Cisco IMC Software version falls within the affected ranges AND the web-based management interface is enabled AND you have read-only users configured in the system.
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 data1.52.03.0
Apply the relevant Cisco IMC software update/patch to remediate the authorization bypass vulnerability.
Fix this in Unified Computing System
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2019-1863 — 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-2019-1863 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