CVE-2018-5481
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 · uneditedOnCommand Unified Manager for 7-Mode (core package) prior to 5.2.4 uses cookies that lack the secure attribute in certain circumstances making it vulnerable to impersonation via man-in-the-middle (MITM) attacks.
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 confidenceOnCommand Unified Manager for 7-Mode fails to set the 'Secure' flag on session cookies, allowing them to be transmitted over unencrypted HTTP connections. An attacker performing a man-in-the-middle attack on the network can intercept these unprotected cookies and use them to impersonate legitimate users.
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< 5.2.4CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify OnCommand Unified Manager version via web interfaceLog into the OnCommand Unified Manager web UI and navigate to the About or Help section to view the installed version numberAffected if Installed version is less than 5.2.4
-
Identify OnCommand Unified Manager version via command lineAccess the server hosting OnCommand Unified Manager and run the appropriate package manager or version command (such as rpm -q or dpkg -l for Linux-based installations) to retrieve the installed package versionAffected if Installed version is less than 5.2.4
-
Confirm the 7-Mode variantVerify that the affected installation is OnCommand Unified Manager for 7-Mode specifically (not the cluster-mode variant), as indicated in the product name or documentationAffected if The product is OnCommand Unified Manager for 7-Mode and version is less than 5.2.4
-
Verify HTTP access capabilityCheck whether the OnCommand Unified Manager server is configured to accept HTTP (non-HTTPS) connections, as the vulnerability allows unprotected cookie transmission over unencrypted channelsAffected if HTTP access is enabled and the version is less than 5.2.4
The environment is affected if OnCommand Unified Manager for 7-Mode version is below 5.2.4, regardless of whether HTTPS is preferred, because the missing Secure flag on cookies permits their exposure during HTTP connections.
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 data5.2.4
Upgrade to OnCommand Unified Manager for 7-Mode core package version 5.2.4 or later, which includes the Secure flag on cookies. Alternatively, ensure all connections use HTTPS and configure cookies to include the Secure attribute.
- 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-2018-5481 — 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-2018-5481 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