dbcve.org
Aws Codecommit TriggerApplication · Jenkins

CVE-2023-41944

MEDIUM · 6.1 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to after 3.0.12 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 escape the queue name parameter passed to a form validation URL, when rendering an error message, resulting in an HTML injection vulnerability.

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 Jenkins AWS CodeCommit Trigger Plugin versions 3.0.12 and earlier contains an HTML injection vulnerability. The queue name parameter passed to a form validation URL is not properly escaped when rendered in an error message, allowing an attacker to inject malicious HTML or script content.

MitigationUpdate to a patched version of the AWS CodeCommit Trigger Plugin when available. Until then, apply input validation and sanitization to the queue name parameter before rendering in error messages.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 AWS CodeCommit Trigger Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'AWS CodeCommit Trigger' or 'aws-codecommit-trigger' to confirm the plugin is present.
    Affected if The plugin is listed as installed.
  2. Identify the installed plugin version
    In the Installed Plugins list, locate the 'AWS CodeCommit Trigger' plugin and note the Version column. Compare this version number to 3.0.12.
    Affected if The installed version is 3.0.12 or earlier.
  3. Confirm access to form validation endpoint
    The vulnerability exists in the form validation URL that accepts a queue name parameter. Check if you have access to trigger configurations or job configurations that use AWS CodeCommit Trigger, particularly where queue name can be specified and validated.
    Affected if You can access job configurations or trigger settings that invoke the form validation with a queue name parameter.
  4. Inspect error message rendering (if accessible)
    If you have a test environment, trigger a validation error on the queue name parameter by submitting invalid input. Examine whether the error message reflects the raw queue name value without escaping.
    Affected if Error messages display the queue name unescaped, allowing injected HTML or script content to render.

You are affected if the AWS CodeCommit Trigger Plugin version 3.0.12 or earlier is installed and users can access the form validation endpoint with queue name input.

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

Update to a patched version of the AWS CodeCommit Trigger Plugin when available. Until then, apply input validation and sanitization to the queue name parameter before rendering in error messages.

Recommended fix Moderate confidence

AWS CodeCommit Trigger Plugin version 3.0.13 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate the 'AWS CodeCommit Trigger' plugin
  3. Check the current version - if it is 3.0.12 or earlier, an update is required
  4. If an update is available, select the plugin and click 'Update'
  5. Alternatively, download the fixed version (3.0.13 or later) from the Jenkins plugin repository and upload it manually via 'Advanced' > 'Upload Plugin'
  6. Restart Jenkins to complete the plugin update

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

Fix this in Aws Codecommit Trigger Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-41944 — 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-41944 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