dbcve.org
Test Results AggregatorApplication · Jenkins

CVE-2023-37956

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 1.2.13 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A missing permission check in Jenkins Test Results Aggregator Plugin 1.2.13 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials.

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 confidence

The Jenkins Test Results Aggregator Plugin versions 1.2.13 and earlier lacks a permission check in certain endpoints, allowing any user with basic Overall/Read permission to make the Jenkins server connect to arbitrary URLs using attacker-specified credentials. This creates a Server-Side Request Forgery (SSRF) vector that can also be leveraged to exfiltrate credentials stored in Jenkins to attacker-controlled endpoints.

MitigationUpdate the Test Results Aggregator Plugin to the latest version (after 1.2.13) which includes proper permission checks. Additionally, review user permissions and monitor for unauthorized outbound connections from 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
Test Results AggregatorApplication
Affected:<= 1.2.13

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Test Results Aggregator plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Test Results Aggregator' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version of the plugin
    On the Installed plugins page, locate the Test Results Aggregator plugin and note the version number displayed in the Version column
    Affected if The installed version is 1.2.13 or earlier
  3. Check plugin configuration for credential usage
    Navigate to Jenkins > Manage Jenkins > Configure System and look for Test Results Aggregator configuration sections; inspect any configured credentials or endpoints
    Affected if Credentials are stored in the plugin configuration and the plugin version is vulnerable
  4. Verify endpoint accessibility without authentication
    Attempt to access common Test Results Aggregator endpoints (such as /testresultsaggregator/ or similar paths) using a low-privileged account that has only Overall/Read permission
    Affected if The endpoint responds without requiring elevated permissions
  5. Audit Jenkins for outbound connections
    Review Jenkins system logs and network logs for any outbound connections from the Jenkins server to unexpected or attacker-controlled URLs
    Affected if Unexpected outbound connections are present in logs originating from Jenkins

A user is affected if the Test Results Aggregator plugin is installed at version 1.2.13 or earlier and any user with basic Overall/Read permission can access plugin endpoints without additional permission checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.2.13
Interim mitigation

Update the Test Results Aggregator Plugin to the latest version (after 1.2.13) which includes proper permission checks. Additionally, review user permissions and monitor for unauthorized outbound connections from the Jenkins server.

Recommended fix Moderate confidence

1.2.14

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab
  3. Locate 'Test Results Aggregator' in the list
  4. If an upgrade is available, select the plugin and click 'Upgrade'
  5. Restart Jenkins if required to complete the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Test Results Aggregator Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-37956 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-37956 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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