Cloudbees Aws CredentialsApplication · Jenkins
CVE-2022-27198
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 cross-site request forgery (CSRF) vulnerability in Jenkins CloudBees AWS Credentials Plugin 189.v3551d5642995 and earlier allows attackers with Overall/Read permission to connect to an AWS service using an attacker-specified token.
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 CSRF vulnerability in the CloudBees AWS Credentials Plugin for Jenkins. Attackers with Overall/Read permission can trigger authenticated requests that connect to AWS services using an attacker-specified token, effectively allowing credential hijacking through cross-site request forgery.
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
Cloudbees Aws CredentialsApplication
<= 189.v3551d5642995>= 1.28, < 1.28.2= 1.32CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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 CloudBees AWS Credentials Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'CloudBees AWS Credentials' or 'aws-credentials' in the plugin list. Alternatively, inspect the $JENKINS_HOME/plugins directory for a folder named 'aws-credentials' or similar.Affected if The plugin is present in the Jenkins instance
-
Check installed plugin version against affected rangesIn Manage Jenkins > Manage Plugins > Installed, locate the CloudBees AWS Credentials plugin and note the version number displayed. Compare it to the affected versions: <= 189.v3551d5642995, >= 1.28 but < 1.28.2, or exactly 1.32.Affected if The installed version matches any of the affected version ranges (189.v3551d5642995 or lower, 1.28.x before 1.28.2, or 1.32)
-
Confirm Overall/Read permission is granted to usersNavigate to Manage Jenkins > Manage Users and then check Manage Jenkins > Configure Global Security > Authorization. Look for whether 'Overall/Read' permission is enabled for authenticated users or specific users/groups.Affected if Overall/Read permission is granted to any user beyond administrators (this permission level is required for the attacker to exploit the CSRF flaw)
-
Identify configured AWS credentials providersNavigate to Manage Jenkins > Credentials > System > Global credentials (or look in the AWS Credentials plugin configuration area). Check if any AWS credentials are configured for Jenkins to use.Affected if AWS credentials are stored or configured in Jenkins (the CSRF flaw allows attackers to hijack these credentials)
-
Review recent AWS API activity for suspicious tokensCheck AWS CloudTrail logs for API calls originating from Jenkins-assumed roles that show unexpected token usage patterns, unusual service access, or requests from unfamiliar IP addresses occurring around the time of suspected exploitation.Affected if AWS API calls show usage of credentials that do not match your legitimate AWS identity or show unexpected activity patterns
A Jenkins instance is affected if it has CloudBees AWS Credentials Plugin version 189.v3551d5642995 or lower, 1.28.x before 1.28.2, or exactly 1.32, AND has Overall/Read permission enabled for non-admin users, AND has AWS credentials configured.
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.
dbcve · scoped1.28.2
Update CloudBees AWS Credentials Plugin to version 190.v71e6c8d2a_3e1 or later, which includes CSRF protection fixes. If immediate update is not possible, restrict Overall/Read permissions and monitor for suspicious AWS API calls.
Upgrade to CloudBees AWS Credentials plugin version 1.33 or later (or 1.28.2+ if staying on 1.28.x branch)
- 1. Navigate to the Jenkins plugin manager (Manage Jenkins > Manage Plugins)
- 2. Locate the CloudBees AWS Credentials plugin in the Installed tab
- 3. Check the current version of the plugin installed
- 4. If running version 1.32, upgrade to version 1.33 or later
- 5. If running version 1.28.x (where x < 2), upgrade to version 1.28.2 or later
- 6. If running an older version (< 1.28), upgrade to the latest available version
- 7. Restart Jenkins to apply the plugin update
- 8. Verify the new version is installed correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Cloudbees Aws Credentials
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-2022-27198 — 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-2022-27198 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