Orka By MacstadiumApplication · Jenkins
CVE-2023-37949
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 permission check in Jenkins Orka by MacStadium Plugin 1.33 and earlier allows 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 Orka by MacStadium Plugin versions 1.33 and earlier lacks proper permission checks, allowing any user with Overall/Read permission (the lowest privilege level) to trigger the plugin to connect to attacker-controlled URLs using attacker-specified credentials IDs. This enables credential harvesting through SSRF-like behavior, as the plugin will transmit credentials to malicious endpoints.
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
Orka By MacstadiumApplication
< 1.34CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Verify if Orka by MacStadium plugin is installedNavigate to the Jenkins plugin management interface and search for 'Orka' or 'MacStadium' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Determine installed version of the Orka pluginLocate the version number for the Orka by MacStadium plugin in the plugin manager's version columnAffected if The version is 1.33 or earlier (anything below 1.34)
-
Review users with Overall/Read permissionCheck the Jenkins global security configuration to identify which users or groups have been granted Overall/Read permissionAffected if Any untrusted or unknown users possess Overall/Read permission
-
Audit configured credentialsReview any credentials configured for use with the Orka plugin, looking for unfamiliar credential IDs that may have been added by an attackerAffected if Unexpected credentials or credential IDs exist in the Orka plugin configuration
-
Check for suspicious outbound connection logsReview Jenkins logs and network monitoring for outbound connections from the Jenkins server to unfamiliar or external URLs, particularly those initiated by the Orka pluginAffected if Connections are observed to attacker-controlled or unexpected external endpoints
A user is affected if the Orka by MacStadium plugin version is 1.33 or earlier AND untrusted users have Overall/Read permission, enabling them to trigger credential transmission to malicious URLs.
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 · scoped1.34
Upgrade the Orka by MacStadium Plugin to version 1.34 or later, which includes proper permission checks. If immediate upgrade is not possible, restrict Overall/Read permission to only trusted users and monitor for unusual outbound connections.
Orka by MacStadium plugin version 1.34 or later
- Navigate to Manage Jenkins > Manage Plugins
- Go to the Available tab and search for 'Orka by MacStadium'
- Select the plugin and click 'Download now and install after restart'
- After Jenkins restarts, verify the plugin version is 1.34 or later under Manage Plugins > Installed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Orka By Macstadium
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37949 — 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-37949 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