CVE-2019-11403
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 · uneditedIn Gradle Enterprise before 2018.5.2, Build Cache Nodes would reflect the configured password back when viewing the HTML page source of the settings page.
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 confidenceGradle Enterprise Build Cache Nodes before version 2018.5.2 expose configured passwords in plaintext within the HTML source code of the settings page, allowing any user with access to view page source to retrieve the 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< 5.2< 2018.5.2CVSS 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.1/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 the installed productLocate the Gradle Enterprise or Gradle Build Cache Node installation and determine which product is running. Check the application's login page, admin interface, or installation documentation for the product name.Affected if The product is Gradle Enterprise or Gradle Build Cache Node
-
Determine the installed versionAccess the admin interface or check the installation files for the version number. This is typically visible in the footer of the web interface or in the installation configuration.Affected if The version is Gradle Build Cache Node < 5.2 or Gradle Enterprise < 2018.5.2
-
Access the settings pageLog in to the web interface and navigate to the settings or configuration page where passwords for external systems (such as repository credentials or remote cache authentication) are configured.Affected if The settings page is accessible to any authenticated user
-
Inspect HTML page source for passwordsWhile on the settings page, view the page source (typically via browser right-click > View Page Source or Ctrl+Shift+I) and search for password values in plaintext within the HTML.Affected if Plaintext passwords appear in the HTML source code of the settings page
The environment is affected if the installed version is Gradle Build Cache Node before 5.2 or Gradle Enterprise before 2018.5.2 AND plaintext passwords are visible in the HTML source of the settings page.
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 · scoped5.22018.5.2
Upgrade Gradle Enterprise to version 2018.5.2 or later to eliminate password reflection in HTML page source.
Gradle Enterprise 2018.5.2 or later / Build Cache Node 5.2 or later
- Back up the current Gradle Enterprise installation and database
- Download Gradle Enterprise version 2018.5.2 or later (for Enterprise), or Build Cache Node version 5.2 or later
- Stop the current Gradle Enterprise or Build Cache Node service
- Install the upgraded version following standard Gradle upgrade procedures
- Restart the Gradle Enterprise or Build Cache Node service
- Verify the fix by viewing the HTML source of the settings page and confirming the password is no longer reflected in the page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11403 — 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-11403 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