CVE-2019-11652
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 · uneditedA potential authorization bypass issue was found in Micro Focus Self Service Password Reset (SSPR) versions prior to: 4.4.0.3, 4.3.0.6, and 4.2.0.6. Upgrade to Micro Focus Self Service Password Reset (SSPR) SSPR versions 4.4.0.3, 4.3.0.6, or 4.2.0.6 as appropriate.
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 confidenceAuthorization bypass vulnerability in Micro Focus Self Service Password Reset (SSPR) allowing unauthorized users to potentially reset passwords or gain access without proper authentication. The CVSS 9.8 indicates complete compromise of confidentiality, integrity, and availability.
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>= 4.2.0.0, < 4.2.0.6>= 4.3.0.0, < 4.3.0.6>= 4.4.0.0, < 4.4.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SSPR is installedLocate the Micro Focus or NetIQ Self Service Password Reset installation directory, or check for the SSPR web application running on your application server (typically under /opt/netiq/sspr, /opt/microfocus/sspr, or within the application server's webapps directory).Affected if SSPR is present in the environment
-
Determine the installed SSPR versionCheck the SSPR version by viewing the version file in the installation directory, accessing the SSPR about page via the web interface (typically /sspr/admin/about or /sspr/about), or querying the installed package via system package manager if installed as an RPM or similar.Affected if The version cannot be determined or is not clearly displayed
-
Compare version to affected rangesCompare the installed version number against these vulnerable ranges: 4.2.0.0 through 4.2.0.5, 4.3.0.0 through 4.3.0.5, and 4.4.0.0 through 4.4.0.2. Versions within any of these ranges are affected.Affected if The installed version falls within any of the specified vulnerable ranges (4.2.x below 4.2.0.6, 4.3.x below 4.3.0.6, or 4.4.x below 4.4.0.3)
-
Verify SSPR web interface exposureConfirm the SSPR web interface is network-accessible (check your web server configuration for SSPR endpoints such as /sspr/public/* or /sspr/user/*). The vulnerability allows unauthorized password resets, so external accessibility increases exposure risk.Affected if The SSPR web interface is externally accessible or not properly firewalled
If SSPR is installed and the version falls within 4.2.0.0-4.2.0.5, 4.3.0.0-4.3.0.5, or 4.4.0.0-4.4.0.2, the environment is affected by this authorization bypass vulnerability.
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.
dbcve · scoped4.2.0.64.3.0.64.4.0.3
Upgrade to SSPR versions 4.4.0.3, 4.3.0.6, or 4.2.0.6 as appropriate for your current version branch to remediate the authorization bypass.
4.2.0.6, 4.3.0.6, or 4.4.0.3 (depending on current branch)
- Identify the currently installed SSPR version (4.2.x, 4.3.x, or 4.4.x branch)
- Download the appropriate fixed version from NetIQ/Micro Focus: 4.2.0.6 for 4.2.x branch, 4.3.0.6 for 4.3.x branch, or 4.4.0.3 for 4.4.x branch
- Review NetIQ/Micro Focus upgrade documentation for SSPR
- Apply the upgrade following standard upgrade procedures
- Verify the installed version matches the target fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation4.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 $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11652 — 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-11652 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