MavenApplication · Jenkins
CVE-2019-10358
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 · uneditedJenkins Maven Integration Plugin 3.3 and earlier did not apply build log decorators to module builds, potentially revealing sensitive build variables in the build log.
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 confidenceThe Jenkins Maven Integration Plugin versions 3.3 and earlier failed to apply build log decorators to Maven module builds. Build log decorators are meant to filter sensitive information (passwords, tokens, credentials) from build output. This oversight allowed sensitive build variables to be exposed in plaintext within build logs for module-level builds.
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
MavenApplication
<= 3.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Maven Integration Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Maven Integration' plugin in the listAffected if Plugin is not found in the installed plugins list
-
Determine installed plugin versionIn the same plugin manager, locate the Maven Integration plugin and note the version number displayed in the version columnAffected if Version is 3.3 or earlier
-
Identify Maven module-based jobsReview Jenkins job history and look for Maven projects configured with multi-module builds (check job configuration for modules or verify build logs contain module-specific output)Affected if Maven jobs with module builds have been executed
-
Inspect build logs for sensitive data exposureOpen build logs from Maven module builds and search for plaintext sensitive values such as passwords, API tokens, or credential variables that should have been filtered by log decoratorsAffected if Build logs from module-level Maven builds contain plaintext sensitive variables like passwords, tokens, or credentials
You are affected if the Maven Integration Plugin version is 3.3 or earlier AND Maven module builds have been run containing sensitive environment variables or credentials.
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 dataUpgrade the Jenkins Maven Integration Plugin to version 3.4 or later to ensure build log decorators are applied to all module builds. Review historical build logs for potential exposure of sensitive variables.
Fix this in Maven
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing3.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10358 — 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-10358 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