M2releaseApplication · Jenkins
CVE-2019-10361
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 Release Plugin 0.14.0 and earlier stored credentials unencrypted 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 confidenceThe Jenkins Maven Release Plugin versions 0.14.0 and earlier stores user credentials in plaintext, unencrypted on the Jenkins master filesystem. Any user with operating system-level access to the Jenkins master can read these stored credentials directly from the file system.
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
M2releaseApplication
<= 0.14.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm M2release plugin is installedCheck the Jenkins plugins directory (typically $JENKINS_HOME/plugins/) or use the Jenkins CLI: jenkins-cli.jar or the web UI to list installed plugins. Look for 'm2release' or 'Maven Release Plugin'.Affected if The plugin is present on the Jenkins master
-
Identify the installed M2release plugin versionExamine the plugin's manifest or metadata file in $JENKINS_HOME/plugins/m2release/META-INF/MANIFEST.MF, or check the plugin's .hpi file. The version is listed as 'Plugin-Version' or in the manifest.Affected if The version is 0.14.0 or earlier
-
Locate credential storage files used by the pluginSearch for credential-related configuration files under $JENKINS_HOME/plugins/m2release/ and any associated Maven settings or credential cache directories that the plugin may use for storing build credentials.Affected if Credential files or configuration files storing credentials exist in the plugin directory or related Maven configuration areas
-
Inspect credential file contents for encryptionOpen the stored credential files found in the previous step using a text editor or command (cat/head). Examine whether the credential values appear as plaintext (readable alphanumeric strings) or are encrypted/hashed (non-readable characters, base64 encoded, or encrypted blocks).Affected if Credentials are stored in plaintext readable format rather than being encrypted or obfuscated
A user is affected if the M2release plugin version 0.14.0 or earlier is installed AND credential files in the plugin's storage areas contain plaintext, readable passwords 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 dataUpdate the Jenkins Maven Release Plugin to a version newer than 0.14.0 where credentials are properly encrypted. Additionally, restrict filesystem access to the Jenkins master and rotate any credentials that may have been exposed.
Fix this in M2release
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10361 — 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-10361 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