dbcve.org
Beaker BuilderApplication · Jenkins

CVE-2019-10398

MEDIUM · 5.5 CVSS v3.1 Published 2019-09-12
Fix available
A fix is available. Upgrade to after 1.9 or later.
See remediation →
57/100
Remediation priority · Elevated
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
Jenkins Beaker Builder Plugin 1.9 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they could be viewed by users with access to the master file system.

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 confidence

The Jenkins Beaker Builder Plugin version 1.9 and earlier stores credentials in plain text (unencrypted) within its global configuration file on the Jenkins master. Users with filesystem access to the Jenkins master can directly read these stored credentials.

MitigationUpgrade the Beaker Builder Plugin to version 1.10 or later, which encrypts credentials. If the instance was compromised, rotate all credentials that were stored in the affected configuration file.

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
Beaker BuilderApplication
Affected:<= 1.9

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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. Check Beaker Builder plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed and locate 'Beaker Builder' in the plugin list, or inspect the plugin's MANIFEST.MF file in $JENKINS_HOME/plugins/beaker-builder/
    Affected if Version is 1.9 or earlier
  2. Locate the plugin configuration file
    On the Jenkins master filesystem, navigate to the Jenkins home directory and find the Beaker Builder plugin configuration (typically stored in $JENKINS_HOME/plugins/beaker-builder/config.xml or within the main Jenkins configuration XML files)
    Affected if The configuration file exists and contains credential storage settings
  3. Inspect for plain text credentials
    Open the configuration file and examine any credential-related fields. Look for username, password, or secret fields and verify whether the values appear as readable plain text or as encrypted/hashed strings
    Affected if Credential values are stored as plain text rather than being encrypted

If the Beaker Builder plugin version is 1.9 or earlier and its configuration file contains plain text (unencrypted) credentials, the environment is affected by this CVE.

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 a release after 1.9
Interim mitigation

Upgrade the Beaker Builder Plugin to version 1.10 or later, which encrypts credentials. If the instance was compromised, rotate all credentials that were stored in the affected configuration file.

Fix this in Beaker Builder Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-10398 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-10398 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