CVE-2019-0405
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 · uneditedSAP Enable Now, before version 1911, leaks information about the existence of a particular user which can be used to construct a list of users, leading to a user enumeration vulnerability and Information Disclosure.
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 confidenceSAP Enable Now before version 1911 contains an information disclosure vulnerability that reveals whether specific usernames exist in the system. Attackers can exploit this to enumerate valid user accounts by repeatedly querying the system with different username variations, potentially building a complete user list for further attacks.
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< 1911CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SAP Enable Now installationCheck for SAP Enable Now installation directory (commonly C:\Program Files\SAP\SAP Enable Now or /opt/sap/enable_now) or look for the 'Enable Now' service running on the systemAffected if SAP Enable Now is installed on the system
-
Determine installed versionLocate the version information in the installation directory, typically in a version.txt, about dialog, or check the installer metadata. The version format is YYMM (e.g., 1911 for November 2019)Affected if The installed version is earlier than 1911 (e.g., 1905, 1809, etc.)
-
Verify web interface accessibilityCheck if the SAP Enable Now web portal (typically on port 8080 or 443) is exposed and accessible from the network. This is the attack surface for user enumerationAffected if The web interface is accessible externally or by unauthorized network users
-
Test for user enumeration vulnerabilitySend HTTP requests to the login or user lookup endpoints with different usernames and observe the response differences. The vulnerability allows attackers to distinguish between valid and invalid usernames based on error messages or response timesAffected if The system returns different responses for existing vs. non-existing usernames, allowing enumeration
The environment is affected if SAP Enable Now version is installed and is earlier than version 1911, and the web interface is accessible to potential attackers.
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 data1911
Upgrade SAP Enable Now to version 1911 or later to receive the vendor patch that addresses the user enumeration vulnerability.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0405 — 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-0405 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