FortifyApplication · Jenkins
CVE-2023-4303
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 Fortify Plugin 22.1.38 and earlier does not escape the error message for a form validation method, 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 confidenceThe Jenkins Fortify Plugin versions 22.1.38 and earlier contains an HTML injection vulnerability in its form validation error message handling. The error message returned by a form validation method is not properly escaped before being rendered in the web interface, allowing an attacker to inject arbitrary HTML into the page.
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
FortifyApplication
< 22.2.39CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Jenkins Fortify Plugin installationIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, or check the plugin file on the Jenkins controller at $JENKINS_HOME/plugins/fortify/WEB-INF/MANIFEST.MFAffected if The Fortify Plugin is not found in the Jenkins plugin directory
-
Identify the installed Fortify Plugin versionRead the version from the MANIFEST.MF file (look for Implementation-Version or Plugin-Version), or view the version column in the Jenkins UI Manage Plugins pageAffected if The version displayed is 22.1.38 or earlier, or shows no version (missing/corrupt manifest)
-
Compare against the fixed versionCheck if the installed version is less than 22.2.39. Note that versions 22.1.39 through 22.2.38 may also be vulnerable depending on when the fix was backportedAffected if The installed version is anything less than 22.2.39
-
Verify the plugin is actively loadedCheck Jenkins logs on startup for successful loading of the fortify plugin, or verify the plugin appears as 'Enabled' in Manage Plugins > InstalledAffected if The plugin is enabled and loaded in Jenkins with a vulnerable version
A user is affected if the Jenkins Fortify Plugin version is installed and is lower than 22.2.39, making HTML injection in form validation error messages possible.
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.
dbcve · scoped22.2.39
Upgrade Jenkins Fortify Plugin to version 22.1.39 or later. If upgrading is not immediately possible, ensure proper HTML output encoding/escaping is applied to all form validation error messages before rendering.
22.2.39
- Log in to Jenkins as an administrator
- Navigate to 'Manage Jenkins' > 'Manage Plugins'
- Click on the 'Updates' tab to view available plugin updates
- Locate 'Fortify Plugin' in the list of available updates
- Check the checkbox next to the Fortify Plugin
- Click 'Download now and install after restart'
- Once downloaded, restart Jenkins to complete the installation
- After restart, verify the plugin version is 22.2.39 or later under 'Manage Plugins' > 'Installed' tab
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortify
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4303 — 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-4303 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