CVE-2023-48222
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 · uneditedRundeck is an open source automation service with a web console, command line tools and a WebAPI. In affected versions access to two URLs used in both Rundeck Open Source and Process Automation products could allow authenticated users to access the URL path, which would allow access to view or delete jobs, without the necessary authorization checks. This issue has been addressed in version 4.17.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.
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 an Insecure Direct Object Reference (IDOR) vulnerability in Rundeck where two specific URLs permit authenticated users to access job resources without proper authorization checks. Successful exploitation allows viewing or deleting jobs that the user should not have access to, representing a broken access control vulnerability.
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>= 4.12.0, < 4.17.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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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.
-
Identify the installed Rundeck versionCheck the Rundeck instance for its version number, typically found in the UI footer, in /opt/rundeck/etc/rundeck-config.properties, or by querying the API endpoint /api/1/system/infoAffected if The version is >= 4.12.0 and < 4.17.3
-
Verify user role configurationsReview Rundeck user roles and ACL policies in the Administration > System ACLs section to confirm which users have job read/delete permissionsAffected if Users with limited roles can access job resources they should not own or be assigned to
-
Audit job access patternsReview Rundeck job audit logs or activity logs to identify if users have been able to view or delete jobs outside their authorized project(s)Affected if Users without project-level or job-level ownership are able to access jobs via direct URL references they were not granted permission to
-
Check for unauthorized job deletionsExamine job deletion logs and compare against expected user permissions to detect if jobs were deleted by users lacking explicit delete grantsAffected if Job deletion events exist for users who should not have had delete permissions on those specific jobs
If the installed Rundeck version falls within 4.12.0 through 4.17.3 and you have multi-user access with role-based restrictions, your environment may be affected by this IDOR vulnerability allowing unauthorized job access.
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 · scoped4.17.3
Upgrade Rundeck to version 4.17.3 or later. No workarounds exist; the vendor recommends immediate upgrade.
4.17.3
- Identify the current Rundeck version using the web UI or CLI
- Download Rundeck version 4.17.3 from the official Rundeck repository or download page
- Review the official Rundeck upgrade documentation for your deployment type
- Backup the existing Rundeck database and configuration files
- Stop the Rundeck service
- Install the 4.17.3 version following standard upgrade procedures
- Start the Rundeck service
- Verify the upgrade was successful by checking the version in the web UI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-48222 — 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-48222 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