# CVE-2023-47112: Authenticated users can view job names and groups they do not have authorization to view in Rundeck

> Authenticated users can view unauthorized job names and groups in Rundeck projects due to missing authorization checks on specific endpoints.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Nov 2023
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-xvmv-4rx6-x6jx

## What is CVE-2023-47112?

CVE-2023-47112 is a medium-severity missing authorization vulnerability in rundeck, published on 16 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Rundeck 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 provides a list of job names and groups for any project, without the necessary authorization checks. The output of these endpoints only exposes the name of job groups and the jobs contained within the specified project. The output is read-only and the access does not allow changes to the information. This vulnerability has been patched in version 4.17.3. Users are advised to upgrade. Users unable to upgrade may block access to the two URLs used in either Rundeck Open Source or Process Automation products at a load balancer level.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2023-47112?

2 open source packages ship an affected version, including org.rundeck:rundeckapp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.rundeck:rundeckapp` | Maven | From 4.17.0 | 4.17.3 |
| `org.rundeck:rundeckapp` | Maven | From 4.17.0 | 4.17.3 |

Products: Pagerduty Rundeck.

## How do I fix CVE-2023-47112?

Upgrade org.rundeck:rundeckapp to 4.17.3 or later.

## Is CVE-2023-47112 being exploited?

There is no known exploitation of CVE-2023-47112 in the wild and no public exploit code.

## Other vulnerabilities in rundeck

- [CVE-2022-29186](https://insights.sbomify.com/CVE-2022-29186/): Use of Hard-coded Cryptographic Key in rundeck/rundeck, rundeckpro/enterprise (critical 9.1)
- [CVE-2021-39132](https://insights.sbomify.com/CVE-2021-39132/): YAML deserialization can run untrusted code (high 8.8)
- [CVE-2023-48222](https://insights.sbomify.com/CVE-2023-48222/): Authenticated users can view or delete jobs they do not have authorization for in Rundeck (high 8.1)
- [CVE-2021-41112](https://insights.sbomify.com/CVE-2021-41112/): Missing Authorization in Rundeck (high 8.1)
- [CVE-2022-31044](https://insights.sbomify.com/CVE-2022-31044/): Plaintext Storage of Keys and Passwords in Rundeck and PagerDuty Process Automation (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47112 and fix it if it is affected.

What it is: CVE-2023-47112 is a medium-severity missing authorization vulnerability in rundeck, published on 16 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-47112 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.rundeck:rundeckapp (Maven): affected from 4.17.0; fixed in 4.17.3
- org.rundeck:rundeckapp (Maven): affected from 4.17.0; fixed in 4.17.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-47112/ (Markdown: https://insights.sbomify.com/CVE-2023-47112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-47112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-47112
- OSV: https://osv.dev/vulnerability/CVE-2023-47112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-47112/
Summaries are generated and may contain mistakes; the official description above is the record.