dbcve.org
Service Management AutomationApplication · Microfocus

CVE-2020-11844

CRITICAL · 9.8 CVSS v3.1 Published 2020-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Incorrect Authorization vulnerability in Micro Focus Container Deployment Foundation component affects products: - Hybrid Cloud Management. Versions 2018.05 to 2019.11. - ArcSight Investigate. versions 2.4.0, 3.0.0 and 3.1.0. - ArcSight Transformation Hub. versions 3.0.0, 3.1.0, 3.2.0. - ArcSight Interset. version 6.0.0. - ArcSight ESM (when ArcSight Fusion 1.0 is installed). version 7.2.1. - Service Management Automation (SMA). versions 2018.05 to 2020.02 - Operation Bridge Suite (Containerized). Versions 2018.05 to 2020.02. - Network Operation Management. versions 2017.11 to 2019.11. - Data Center Automation Containerized. versions 2018.05 to 2019.11 - Identity Intelligence. versions 1.1.0 and 1.1.1. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.

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 confidence

This is an Incorrect Authorization vulnerability in Micro Focus Container Deployment Foundation component. The flaw allows unauthorized access to the container deployment infrastructure, enabling attackers to bypass authentication controls and gain privileged access to the foundation layer that manages container deployments across multiple enterprise products.

MitigationApply vendor patches or updates to move beyond the vulnerable version ranges. Review access controls and audit authorization policies in the Container Deployment Foundation after patching.

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
Service Management AutomationApplication
Affected:= 2018.05= 2018.08= 2018.11= 2019.02= 2019.05= 2019.08= 2019.11= 2020.02

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Service Management Automation version
    Check the product version through the system management console, About page, or version info command specific to Micro Focus Service Management Automation. Common locations include the administrative UI or system information files in the installation directory.
    Affected if The installed version matches any of: 2018.05, 2018.08, 2018.11, 2019.02, 2019.05, 2019.08, 2019.11, or 2020.02
  2. Verify Container Deployment Foundation component is present
    Inspect the installed components or modules within the Service Management Automation environment. Look for the Container Deployment Foundation component in the product's component list or installed services.
    Affected if Container Deployment Foundation is installed as part of the Service Management Automation deployment
  3. Check authentication configuration for Container Deployment Foundation
    Review the authentication and access control configuration files or settings specific to the Container Deployment Foundation component. Look for authorization policies that control access to the deployment infrastructure.
    Affected if Authentication controls are misconfigured or weak authorization policies are in place for the Container Deployment Foundation component
  4. Inspect access controls for the foundation layer
    Examine the access control lists, role definitions, or permission settings that govern access to the foundation layer managing container deployments. Check for any overly permissive or misaligned access rules.
    Affected if The foundation layer has permissive access rules that could allow unauthorized privileged access

A system is affected if it runs any of the listed Service Management Automation versions (2018.05 through 2020.02) with the Container Deployment Foundation component enabled and exposed to unauthorized access due to incorrect authorization controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches or updates to move beyond the vulnerable version ranges. Review access controls and audit authorization policies in the Container Deployment Foundation after patching.

Fix this in Service Management Automation Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-11844 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-11844 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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