# CVE-2019-10474: Jenkins Global Post Script Plugin missing permission check

> Users with Overall/Read access can list scripts stored on the Jenkins master file system due to a missing permission check.

- **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:** No
- **Published:** 23 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-24w5-w6fw-qqx7

## What is CVE-2019-10474?

CVE-2019-10474 is a medium-severity missing authorization vulnerability in Jenkins Global Post Script Plugin, published on 23 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A missing permission check in Jenkins Global Post Script Plugin in allowed users with Overall/Read access to list the scripts available to the plugin stored on the Jenkins master file system.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2019-10474?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:global-post-script. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:global-post-script` | Maven | All versions to 1.1.4 | None |
| `org.jenkins-ci.plugins:global-post-script` | Maven | All versions to 1.1.4 | None |

Products: Jenkins Global Post Script.

## How do I fix CVE-2019-10474?

No fix has been published for CVE-2019-10474 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-10474 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10474 and fix it if it is affected.

What it is: CVE-2019-10474 is a medium-severity missing authorization vulnerability in Jenkins Global Post Script Plugin, published on 23 Oct 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-10474 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:global-post-script (Maven): affected all versions up to 1.1.4; no fix listed
- org.jenkins-ci.plugins:global-post-script (Maven): affected all versions up to 1.1.4; no fix listed

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-2019-10474/ (Markdown: https://insights.sbomify.com/CVE-2019-10474/index.md)
```

## Sources

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

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