dbcve.org
Enterprise DeveloperApplication · Microfocus

CVE-2017-7420

CRITICAL · 9.8 CVSS v3.0 Published 2017-08-21
Fix available
A fix is available. Upgrade to after 2.3 or later.
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
An Authentication Bypass (CWE-287) vulnerability in ESMAC (aka Enterprise Server Monitor and Control) in Micro Focus Enterprise Developer and Enterprise Server 2.3 and earlier, 2.3 Update 1 before Hotfix 8, and 2.3 Update 2 before Hotfix 9 allows remote unauthenticated attackers to view and alter configuration information and alter the state of the running product (CWE-275).

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

Authentication bypass vulnerability in ESMAC (Enterprise Server Monitor and Control) web interface allows remote unauthenticated attackers to bypass authentication controls and access configuration information and manipulate the running product state.

MitigationApply the vendor-supplied hotfixes: Hotfix 8 for Enterprise Server 2.3 Update 1, Hotfix 9 for Update 2, or upgrade to a patched version that includes the authentication fix.

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
Enterprise DeveloperApplication
Affected:= 2.3
Enterprise ServerApplication
Affected:<= 2.3= 2.3
Enterprise Server Monitor And ControlApplication
Affected:all versions

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.0/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 Microfocus product and version
    Locate the Enterprise Server, Enterprise Developer, or Enterprise Server Monitor and Control installation and determine the exact version number (for example, check the product About or version information in the installation directory)
    Affected if The installed version is Microfocus Enterprise Developer 2.3, Enterprise Server 2.3 or any version <= 2.3, or Enterprise Server Monitor and Control of any version
  2. Verify ESMAC web interface is enabled
    Check whether the ESMAC (Enterprise Server Monitor and Control) web interface service or component is installed and running on the system (typically accessible via a web port)
    Affected if ESMAC web interface is installed and accessible on the system
  3. Confirm network accessibility of ESMAC
    Determine if the ESMAC web interface is exposed to network access, either locally or remotely (check listening ports and any firewall or access configuration)
    Affected if The ESMAC web interface is reachable over the network (local or remote)
  4. Verify authentication is active on ESMAC
    Attempt to access the ESMAC web interface without credentials to confirm whether authentication is properly enforced
    Affected if Unauthenticated access to ESMAC is possible without being redirected to a login page or receiving an authentication error

You are affected if you have any version of Enterprise Server Monitor and Control, or Enterprise Server/Developer version 2.3 or lower, with the ESMAC web interface enabled and accessible, and unauthenticated access is possible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.3
Interim mitigation

Apply the vendor-supplied hotfixes: Hotfix 8 for Enterprise Server 2.3 Update 1, Hotfix 9 for Update 2, or upgrade to a patched version that includes the authentication fix.

Recommended fix High confidence
  1. Identify the installed version and update level of Micro Focus Enterprise Developer or Enterprise Server (e.g., 2.3, 2.3 Update 1, or 2.3 Update 2)
  2. For Enterprise Developer or Enterprise Server 2.3 Update 1: Apply Hotfix 8 or later from Micro Focus support
  3. For Enterprise Developer or Enterprise Server 2.3 Update 2: Apply Hotfix 9 or later from Micro Focus support
  4. For Enterprise Server Monitor And Control (all versions): Apply the corresponding hotfix from Micro Focus support for the installed base version
  5. Restart the Enterprise Server services as required by the hotfix installation
  6. Verify the ESMAC interface is accessible only after proper authentication

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Enterprise Developer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7420 — 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-2017-7420 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