CVE-2019-3489
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 · uneditedAn unauthenticated file upload vulnerability has been identified in the Web Client component of Micro Focus Content Manager 9.1, 9.2, and 9.3 when configured to use the ADFS authentication method. The vulnerability could be exploited by an unauthenticated remote attacker to upload content to arbitrary locations on the Content Manager 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 · high confidenceAn unauthenticated file upload vulnerability in the Web Client component of Micro Focus Content Manager versions 9.1, 9.2, and 9.3 when configured to use ADFS authentication allows remote attackers to upload files to arbitrary locations on the server without any authentication credentials.
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>= 9.1, <= 9.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installed Content Manager versionCheck the application or Windows Programs and Features for 'Micro Focus Content Manager' and note the exact version number (9.1, 9.2, or 9.3)Affected if The installed version falls within 9.1 through 9.3 inclusive
-
Confirm ADFS authentication is enabledAccess the Content Manager administration console or configuration settings and locate the authentication configuration. Look for settings related to ADFS (Active Directory Federation Services) or SAML-based authentication being active.Affected if ADFS authentication is configured and enabled for the Web Client
-
Verify Web Client component is accessibleCheck if the Content Manager Web Client interface is exposed by attempting to access the web URL or reviewing web server configuration for Content Manager endpointsAffected if The Web Client is reachable over the network and ADFS authentication is in use
-
Inspect ADFS configuration for authentication enforcementReview the ADFS configuration on the server to confirm whether it properly enforces authentication challenges before allowing access to file upload functionalityAffected if ADFS is configured but may not be properly validating sessions before allowing file operations
You are affected if Content Manager version 9.1, 9.2, or 9.3 is installed AND ADFS authentication is enabled for the Web Client component, as this combination allows unauthenticated file uploads.
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 dataIf ADFS authentication is not required, disable it. Otherwise, apply vendor-supplied patches for this vulnerability and verify that file upload functionality properly enforces authentication and path restrictions.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3489 — 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-2019-3489 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