Testquality UpdaterApplication · Jenkins
CVE-2023-24453
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 missing check in Jenkins TestQuality Updater Plugin 1.3 and earlier allows attackers with Overall/Read permission 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 confidenceThe Jenkins TestQuality Updater Plugin 1.3 and earlier lacks proper authorization checks, allowing any user with Overall/Read permission (the lowest privilege level) to make arbitrary HTTP requests to attacker-specified URLs using attacker-specified credentials. This Server-Side Request Forgery (SSRF) vulnerability enables authenticated attackers to interact with internal services or exfiltrate data through the Jenkins server.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Verify TestQuality Updater Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'TestQuality Updater', or query the Jenkins API at /pluginManager/plugin/TestQuality Updater to list installed plugins.Affected if The TestQuality Updater plugin appears in the installed plugins list.
-
Check the installed version of TestQuality Updater PluginIn the Installed Plugins tab, locate the TestQuality Updater entry and note the Version column. Alternatively, query the API endpoint /pluginManager/plugin/TestQuality Updater and extract the 'version' field from the JSON response.Affected if The version listed is 1.3 or earlier.
-
Confirm plugin is active and loadedIn Manage Jenkins > Manage Plugins > Installed, verify the TestQuality Updater plugin shows as 'Enabled' or 'Active'. Check the 'Enabled' status via the API at /pluginManager/plugin/TestQuality Updater.Affected if The plugin is enabled and loaded into Jenkins.
-
Verify user access to plugin endpointThe vulnerability allows any user with Overall/Read permission to access the plugin's HTTP request feature. Check if unauthenticated or low-privilege users can access the endpoint at /plugin/TestQuality Updater/ or related endpoints by testing with a user who has only Overall/Read permission.Affected if Users with only Overall/Read permission can trigger HTTP requests through the plugin interface.
You are affected if the TestQuality Updater Plugin version 1.3 or earlier is installed and enabled in your Jenkins instance, allowing low-privilege users to make arbitrary HTTP requests.
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 version 1.4 or later, which includes proper authorization checks to prevent unauthorized HTTP requests.
Fix this in Testquality Updater
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-24453 — 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-24453 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