Octoperf Load TestingApplication · Jenkins
CVE-2023-28672
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 OctoPerf Load Testing Plugin Plugin 4.5.1 and earlier does not perform a permission check in a connection test HTTP endpoint, allowing attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
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 OctoPerf Load Testing Plugin before version 4.5.2 fails to enforce permission checks on a connection test HTTP endpoint. While the endpoint requires Overall/Read permission, it should require elevated privileges for credential operations. An attacker with basic read access can specify arbitrary URLs and credential IDs to trigger connections to external systems, potentially exfiltrating stored Jenkins credentials.
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
Octoperf Load TestingApplication
<= 4.5.1CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 OctoPerf Load Testing Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed and search for 'OctoPerf Load Testing' or inspect the plugin directory (typically $JENKINS_HOME/plugins/ for files starting with 'octoperf-load-testing')Affected if The plugin appears in the installed plugins list
-
Identify the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, find OctoPerf Load Testing and note the version number displayed in the Version columnAffected if The installed version is 4.5.1 or lower (any version <= 4.5.1)
-
Confirm Overall/Read permission is grantedNavigate to Jenkins > Manage Jenkins > Configure Global Security or check Authorization Strategy settings. Verify which users or groups have Overall/Read permission enabledAffected if Users beyond trusted administrators have Overall/Read permission enabled in the security configuration
You are affected if the OctoPerf Load Testing Plugin version is 4.5.1 or lower AND untrusted users have Overall/Read permission, allowing them to access the vulnerable connection test endpoint.
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 · scopedUpgrade OctoPerf Load Testing Plugin to version 4.5.2 or later which implements proper permission checks on the connection test endpoint. If immediate upgrade is not possible, restrict Overall/Read permission to trusted users only.
Latest available version of OctoPerf Load Testing Plugin (verify fixed version on Jenkins plugin repository)
- 1. Navigate to Jenkins Manage Plugins page
- 2. Go to the 'Installed' tab
- 3. Locate 'OctoPerf Load Testing Plugin' in the list
- 4. Check if an update is available and upgrade to the latest version
- 5. Alternatively, verify with vendor that the permission check has been added in newer releases
- 6. Restart Jenkins after plugin update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Octoperf Load Testing
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28672 — 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-28672 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