Jenkins Aws Codecommit Trigger vulnerabilities

5 CVEs affecting Jenkins Aws Codecommit Trigger, 0 known to be exploited (CISA KEV), with EPSS scores. Latest: CVE-2023-41944, published 2023-09-06.

Highest priority

Known exploited (CISA KEV) first, then by EPSS exploit probability.

CVE-2023-41943, published 2023-09-06. Medium severity, CVSS 6.5. EPSS: 0.6% chance of exploitation in the next 30 days. Jenkins 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.
CVE-2023-35147, published 2023-06-14. Medium severity, CVSS 6.5. EPSS: 0.6% chance of exploitation in the next 30 days. 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…
CVE-2023-41944, published 2023-09-06. Medium severity, CVSS 6.1. EPSS: 0.5% chance of exploitation in the next 30 days. 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…
CVE-2023-41941, published 2023-09-06. Medium severity, CVSS 4.3. EPSS: 0.4% chance of exploitation in the next 30 days. A missing permission check in Jenkins AWS CodeCommit Trigger Plugin 3.0.12 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of AWS credentials stored in Jenkins.
CVE-2023-41942, published 2023-09-06. Medium severity, CVSS 4.3. EPSS: 0.3% chance of exploitation in the next 30 days. A cross-site request forgery (CSRF) vulnerability in Jenkins AWS CodeCommit Trigger Plugin 3.0.12 and earlier allows attackers to clear the SQS queue.