Testquality UpdaterApplication · Jenkins
CVE-2023-24452
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins TestQuality Updater Plugin 1.3 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified username and password.
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 confidenceThis is a CSRF vulnerability in the Jenkins TestQuality Updater Plugin (versions 1.3 and earlier) that allows attackers to trick authenticated Jenkins users into making unintended requests to attacker-specified URLs with attacker-specified credentials. The lack of CSRF token validation on plugin endpoints enables cross-site request forgery attacks where the victim's authenticated session is leveraged to connect to external systems under attacker control.
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
Testquality UpdaterApplication
<= 1.3CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 if TestQuality Updater plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-pluginsAffected if TestQuality Updater appears in the list of installed plugins
-
Verify the installed version of TestQuality UpdaterIn the Installed plugins tab, locate TestQuality Updater and read the Version column. Alternatively, check the plugin file metadata in the $JENKINS_HOME/plugins/ directoryAffected if Version is 1.3 or lower
-
Confirm the plugin is enabled and activeIn Manage Jenkins > Manage Plugins > Instable tab, verify the plugin shows as 'Enabled' with a blue checkmark, or check the plugin state via the Jenkins APIAffected if Plugin is enabled and appears active in the Jenkins environment
-
Check for active TestQuality webhook or endpoint configurationsLook for TestQuality-related configurations under Manage Jenkins > Configure System, or in job configurations that reference TestQuality Updater plugin featuresAffected if The plugin is actively configured or used in any Jenkins jobs or system settings
You are affected if the TestQuality Updater plugin is installed at version 1.3 or earlier and the plugin is enabled in your Jenkins instance.
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 dataUpgrade the TestQuality Updater Plugin to a version newer than 1.3. If immediate patching is not possible, disable or remove the plugin and verify no other plugins expose similar CSRF vulnerabilities.
Fix this in Testquality Updater
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-24452 — 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-24452 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