Aws Codecommit TriggerApplication · Jenkins
CVE-2023-41943
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 AWS CodeCommit Trigger Plugin 3.0.12 and earlier does not perform a permission check in an HTTP endpoint, allowing attackers with Overall/Read permission to clear the SQS queue.
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 AWS CodeCommit Trigger Plugin versions 3.0.12 and earlier lacks authorization checks on an HTTP endpoint, allowing any authenticated user with Overall/Read permission (the lowest privilege level) to clear configured SQS queues. This is an insecure direct object reference (IDOR) or broken access control vulnerability where the endpoint processes the action without validating the user's permissions beyond basic authentication.
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
<= 3.0.12CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Check installed AWS CodeCommit Trigger Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'AWS CodeCommit Trigger' or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.each { if (it.shortName == 'aws-codecommit-trigger') { println "Version: ${it.version}" } }Affected if The plugin version is 3.0.12 or earlier
-
Verify the plugin has SQS queue configurationsCheck the Jenkins job configuration pages for any jobs using the AWS CodeCommit Trigger, or query the Jenkins configuration.xml files for 'aws-codecommit-trigger' related SQS queue settings under the trigger configuration sectionAffected if Any job is configured with AWS CodeCommit SQS queue triggers
-
Confirm authenticated users with Overall/Read permission existNavigate to Manage Jenkins > Manage Users or use the Jenkins script console: Jenkins.instance.authorizationStrategy.allUsers.each { println "${it.id}: ${it.getOverallRead()}" } to list users who have Overall/Read permissionAffected if Any authenticated user exists with Overall/Read permission (this is the default for authenticated users in standard Jenkins setups)
If the AWS CodeCommit Trigger Plugin version is 3.0.12 or earlier and the plugin is installed with SQS queue configurations, any authenticated user with basic read access can clear the SQS queues.
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 AWS CodeCommit Trigger Plugin to version 3.0.13 or later, which implements proper permission checks on the affected HTTP endpoint. As a compensating control, restrict Overall/Read permission to only trusted users until the patch can be applied.
Fix this in Aws Codecommit Trigger
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-2023-41943 — 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-2023-41943 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