dbcve.org
Aws Codecommit TriggerApplication · Jenkins

CVE-2023-35147

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to after 3.0.12 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Jenkins AWS CodeCommit Trigger Plugin 3.0.12 and earlier does not restrict the AWS SQS queue name path parameter in an HTTP endpoint, allowing attackers with Item/Read permission to obtain the contents of arbitrary files on the Jenkins controller 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 confidence

The AWS CodeCommit Trigger Plugin before version 3.0.13 contains a path traversal vulnerability in an HTTP endpoint that exposes the AWS SQS queue name parameter without proper validation. Attackers with minimal Item/Read permission can manipulate this parameter to read arbitrary files from the Jenkins controller filesystem.

MitigationUpgrade the AWS CodeCommit Trigger Plugin to version 3.0.13 or later which includes proper path parameter validation. As a temporary workaround, restrict Item/Read permissions until the upgrade can be applied.

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
Aws Codecommit TriggerApplication
Affected:<= 3.0.12

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify the AWS CodeCommit Trigger Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed, or inspect the plugin directory at $JENKINS_HOME/plugins/ for a folder named aws-codecommit-trigger or similar
    Affected if The plugin folder exists in the Jenkins plugins directory
  2. Determine the installed plugin version
    Check the plugin's manifest file (META-INF/MANIFEST.MF) inside the plugin folder, or view the version listed in the Jenkins Plugin Manager under Installed tab
    Affected if The version listed is 3.0.12 or lower
  3. Verify if the vulnerable HTTP endpoint is accessible
    Check if the plugin's trigger endpoint is exposed. Inspect the plugin's web.xml or Java code for URL mappings related to 'queue' or 'SQS'. In a default Jenkins setup, look for endpoints under /aws-codecommit-trigger/ or similar paths
    Affected if HTTP endpoints handling SQS queue parameters are reachable without additional authentication beyond basic Jenkins Item/Read
  4. Confirm Item/Read permission is granted to untrusted users
    Review Jenkins authorization matrix at Manage Jenkins > Configure Global Security. Check if 'Overall/Read' or 'Item/Read' permissions are enabled for anonymous users or low-privilege users/groups
    Affected if Anonymous users or non-admin users have Item/Read permissions enabled, allowing them to access the vulnerable endpoint

You are affected if the AWS CodeCommit Trigger Plugin version is 3.0.12 or lower AND the vulnerable SQS queue endpoint is accessible to users with Item/Read permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 3.0.12
Interim mitigation

Upgrade the AWS CodeCommit Trigger Plugin to version 3.0.13 or later which includes proper path parameter validation. As a temporary workaround, restrict Item/Read permissions until the upgrade can be applied.

Recommended fix Moderate confidence

Upgrade to the latest available version of AWS CodeCommit Trigger plugin (version greater than 3.0.12)

  1. 1. Navigate to the Jenkins dashboard and go to 'Manage Jenkins'
  2. 2. Click on 'Manage Plugins'
  3. 3. Select the 'Installed' tab
  4. 4. Locate the 'AWS CodeCommit Trigger' plugin in the list
  5. 5. If an update is available, click 'Update' to install the latest version that includes the security fix
  6. 6. Restart Jenkins to complete the plugin update
Caveat Review release notes for any configuration or behavioral changes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aws Codecommit Trigger Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-35147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-35147 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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