AcutowebApplication · Microfocus

CVE-2019-17087

HIGH · 7.5 CVSS v3.1 Published 2019-12-11
Fix available
A fix is available. Upgrade to 10.3 or later.
See remediation →
84/100
Remediation priority · High
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
Unauthorized file download vulnerability in all supported versions of Micro Focus AcuToWeb. The vulnerability could be exploited to enumerate and download files from the filesystem of the system running AcuToWeb, with the privileges of the account AcuToWeb is running under.

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 confidence

Unauthorized file download vulnerability in Micro Focus AcuToWeb that allows attackers to enumerate and download arbitrary files from the server filesystem through insufficient access controls, likely path traversal. The impact is limited to the filesystem permissions of the account running the AcuToWeb service.

MitigationApply the vendor patch from Micro Focus immediately and verify that AcuToWeb runs with minimal necessary filesystem permissions to limit exposure.

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
AcutowebApplication
Affected:< 10.3

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify if AcuToWeb is installed
    Check common installation directories for AcuToWeb: Windows default is C:\Program Files\Micro Focus\AcuToWeb or C:\Micro Focus\AcuToWeb. On Linux, check /opt/MicroFocus/AcuToWeb or /opt/acutoweb. Look for the acutoweb.exe or acutoweb binary, or check for Micro Focus services running on common ports (8080, 8081).
    Affected if AcuToWeb software is present on the system and the service is installed.
  2. Determine installed AcuToWeb version
    Check the installed version through Windows Programs and Features, or look for a version file in the installation directory (often named version.txt, README, or in the bin directory). If the web interface is accessible, the version may be displayed on the login page or in HTTP headers.
    Affected if The installed version is lower than 10.3.
  3. Verify AcuToWeb service is running and accessible
    Check if the AcuToWeb service process is active. On Windows, use Services.msc or 'sc query AcuToWeb'. On Linux, use 'ps aux | grep acutoweb' or check for the service process. Confirm the web port is listening (commonly 8080 or 8081) using netstat or ss.
    Affected if The AcuToWeb service is running and accepting network connections.
  4. Check filesystem permissions on the service account
    Review the user account under which the AcuToWeb service runs. On Windows, right-click the service in Services.msc and check 'Log On As'. On Linux, check the service init script or systemd unit file for the user directive. Verify what filesystem paths that account can access.
    Affected if The service runs with elevated privileges or has broad filesystem access beyond its application directory.

You are affected if AcuToWeb is installed with a version lower than 10.3 and the service is accessible over the network, as the path traversal flaw can be exploited to read arbitrary files within the service account's filesystem permissions.

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
Upgrade available Upgrade to 10.3 or later
Fixed in 10.3
Interim mitigation

Apply the vendor patch from Micro Focus immediately and verify that AcuToWeb runs with minimal necessary filesystem permissions to limit exposure.

Fix this in Acutoweb Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-17087 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-17087 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