OpenidApplication · Jenkins
CVE-2019-1003099
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 · uneditedA missing permission check in Jenkins openid Plugin in the OpenIdSsoSecurityRealm.DescriptorImpl#doValidate form validation method allows attackers with Overall/Read permission to initiate a connection to an attacker-specified server.
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 confidenceThis is a missing permission check vulnerability in the Jenkins openid Plugin's OpenIdSsoSecurityRealm.DescriptorImpl#doValidate form validation method. Attackers with Overall/Read permission can abuse this to make the Jenkins server initiate connections to attacker-controlled servers, resulting in Server-Side Request Forgery (SSRF).
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
OpenidApplication
<= 2.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Openid plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the CLI: java -jar jenkins-cli.jar list-plugins | grep -i openidAffected if Openid plugin appears in the list with version 2.3 or lower
-
Confirm the plugin is enabledCheck the Jenkins UI at Manage Jenkins > Manage Plugins > Installed - ensure the Openid plugin shows as 'Enabled' or check configuration at Manage Jenkins > Configure Global Security > Security Realm to see if OpenID SSO is configuredAffected if Plugin is enabled or actively used as the security realm
-
Identify users with Overall/Read permissionCheck Manage Jenkins > Manage Users and review authorization settings at Manage Jenkins > Configure Global Security > Authorization. Look for who has Overall/Read access, especially users outside your trusted admin groupAffected if Any untrusted or unexpected users have Overall/Read permission
-
Verify the doValidate endpoint is accessibleAttempt to access the vulnerable endpoint directly or check if the OpenID configuration form at Manage Jenkins > Configure Global Security is reachable by non-admin users with Overall/ReadAffected if The form validation endpoint responds without proper permission checks
You are affected if the Jenkins Openid plugin version 2.3 or lower is installed and enabled, and untrusted users have Overall/Read permission which would allow them to trigger the SSRF via the doValidate method.
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 openid Plugin to the latest patched version that includes proper permission checks in the doValidate method. Until then, limit Overall/Read permission to trusted users only.
Fix this in Openid
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-2019-1003099 — 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-1003099 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