CVE-2021-22504
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 · uneditedArbitrary code execution vulnerability on Micro Focus Operations Bridge Manager product, affecting versions 10.1x, 10.6x, 2018.05, 2018.11, 2019.05, 2019.11, 2020.05, 2020.10. The vulnerability could allow remote attackers to execute arbitrary code on an OBM server.
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 confidenceCritical arbitrary code execution vulnerability in Micro Focus Operations Bridge Manager (OBM) affecting versions 10.1x, 10.6x, and multiple 2018-2020 releases. The vulnerability allows remote unauthenticated attackers to execute arbitrary code on affected OBM servers via an unspecified attack vector.
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= 10.10= 10.11= 10.12= 10.60= 10.61= 10.62= 10.63= 2018.05= 2018.11= 2019.05= 2019.11= 2020.05CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 if OBM is installedLook for Micro Focus Operations Bridge Manager installation directories (typically under /opt/MicroFocus or C:\Program Files\Micro Focus on Windows). Check for OBM-related services or processes running on the system.Affected if OBM software is found running on the system
-
Determine installed OBM versionLocate the OBM version file or use OBM administration tools to retrieve the version number. Common locations include version.info files within the OBM installation directory or via OBM's admin console.Affected if Installed version matches 10.10, 10.11, 10.12, 10.60, 10.61, 10.62, 10.63, 2018.05, 2018.11, 2019.05, 2019.11, or 2020.05
-
Check network exposure of OBM interfacesIdentify ports used by OBM (commonly 8080, 8443, or custom ports). Use netstat or firewall rules to determine if these ports are accessible from untrusted network interfaces or external IP addresses.Affected if OBM web or management interfaces are exposed to the internet or untrusted networks without proper access controls
-
Review for indicators of compromiseExamine OBM server for unexpected new files, unknown user accounts, or suspicious processes. Check OBM logs for unusual authentication attempts, unexpected command executions, or unknown service deployments.Affected if Suspicious files, unauthorized accounts, or anomalous activity is found in OBM directories or logs
A system is affected if it runs any of the listed OBM versions (10.10 through 2020.05) and the vulnerability can be exploited remotely without authentication when OBM interfaces are network-accessible.
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 dataApply vendor-supplied patches for CVE-2021-22504 immediately. Until patches are deployed, restrict network exposure of OBM interfaces to trusted networks only and implement additional monitoring for indicators of compromise.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22504 — 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-2021-22504 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