CVE-2023-4302: Jenkins Fortify Plugin missing permission check

Summary

22/08/2023
Yes i
Moderate
4.2

CVE-2023-4302: Jenkins Fortify Plugin missing permission check. Affects org.jenkins-ci.plugins:fortify versions < 22.2.39. Fixed in 22.2.39. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Fortify Plugin is a Maven ecosystem package that integrates Fortify Static Code Analyzer with Jenkins, enabling users to scan their code for security vulnerabilities. It provides a seamless workflow for analyzing and managing Fortify scan results within the Jenkins environment.

Vulnerability Detail

The Jenkins Fortify Plugin version 22.1.38 and earlier suffers from a missing permission check vulnerability. This vulnerability allows attackers with Overall/Read permission to connect to a specified URL using attacker-specified credentials IDs obtained through another method. By exploiting this vulnerability, attackers can capture credentials stored in Jenkins. Additionally, the affected HTTP endpoints do not require POST requests, making it susceptible to cross-site request forgery (CSRF) attacks. The Fortify Plugin version 22.2.39 addresses this vulnerability by enforcing POST requests and requiring appropriate permissions for the affected HTTP endpoints.

How To Fix

Minimum fixed version

22.2.39

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the latest version of the Jenkins Fortify Plugin.

Conclusion

The Jenkins Fortify Plugin version 22.1.38 and earlier is vulnerable to a missing permission check issue that can lead to unauthorized access and potential data breaches. It is crucial to upgrade to version 22.2.39 or later to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:fortify →

Share this vulnerability

FAQ

This vulnerability allows attackers with Overall/Read permission to capture credentials stored in Jenkins, potentially leading to unauthorized access and data breaches.

Yes, this vulnerability can be exploited remotely by attackers with Overall/Read permission.

There are no known instances of this vulnerability being exploited in the wild at the time of this report.

Yes, the CVSS score for this vulnerability is 4.2.

Yes, you can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:fortify.

How To Fix

Minimum fixed version

22.2.39

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback