OpenshiftApplication · Redhat
CVE-2016-3724
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 before 2.3 and LTS before 1.651.2 allow remote authenticated users with extended read access to obtain sensitive password information by reading a job configuration.
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 confidenceIn affected Jenkins versions before 2.3 and LTS 1.651.2, users with the 'extended read' permission (read-only access to jobs) could view plaintext passwords stored in job configuration XML. This occurred because password fields were not properly masked when rendering job configurations to read-only users.
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
OpenshiftApplication
= 3.1= 3.2
JenkinsApplication
<= 1.649<= 1.651.1CVSS 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.0/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.
-
Check installed Jenkins versionNavigate to Manage Jenkins > About Jenkins or access /api/json?tree=version endpointAffected if Version is 1.649 or earlier for weekly releases, or 1.651.1 or earlier for LTS releases
-
Verify if OpenShift bundled Jenkins is in useCheck the OpenShift version by running 'oc version' or checking the OpenShift cluster versionAffected if OpenShift version is exactly 3.1 or 3.2 and includes bundled Jenkins
-
Identify users with extended read permissionNavigate to Manage Jenkins > Manage Users and review permissions, or inspect the authorization matrix in Configure Global SecurityAffected if Any user or group is granted the Extended Read permission (ExtendedRead permission in matrix)
-
Locate jobs containing password credentialsReview job configurations by examining config.xml files in JENKINS_HOME/jobs/<jobname>/ or via the web UI at each job's Configure pageAffected if Any jobs contain password-type parameters, credentials, or password fields in build configurations
You are affected if running Jenkins 1.649 or earlier (weekly) or 1.651.1 or earlier (LTS), or OpenShift 3.1/3.2, AND you have users with Extended Read permission AND you have jobs containing password fields 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 Jenkins to version 2.3 or later (weekly) or 1.651.2 or later (LTS), which properly masks password fields from users with read-only access. Verify after upgrade that password credentials are no longer visible in job configurations.
Fix this in Openshift
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-3724 — 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-2016-3724 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