CVE-2024-47804

Jenkins provides APIs for fine-grained control of item creation:

• Authorization strategies can prohibit the creation of items of a given type in a given item group (ACL#hasCreatePermission2).

• Item types can prohibit creation of new instances in a given item group (TopLevelItemDescriptor#isApplicableIn(ItemGroup)).

If an attempt is made to create an item of a prohibited type through the Jenkins CLI or the REST API and either of the above checks fail, Jenkins 2.478 and earlier, LTS 2.462.2 and earlier creates the item in memory, only deleting it from disk.

This allows attackers with Item/Create permission to bypass these restrictions, creating a temporary item. With Item/Configure permission, they can also save the item to persist it.

If an attempt is made to create an item of a prohibited type through the Jenkins CLI or the REST API and either of the above checks fail, Jenkins 2.479, LTS 2.462.3 does not retain the item in memory.

An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly. Typical impact: memory safety violations, unexpected behavior, or code execution.

CVE-2024-47804 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.462.3, 2.479); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-47804? CVE-2024-47804 is a medium-severity type confusion vulnerability in org.jenkins-ci.main:jenkins-core (maven), affecting versions < 2.462.3. It is fixed in 2.462.3, 2.479. An object is accessed using a type that is incompatible with its actual type, causing the runtime to interpret memory incorrectly.
2. How severe is CVE-2024-47804? CVE-2024-47804 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.jenkins-ci.main:jenkins-core are affected by CVE-2024-47804? org.jenkins-ci.main:jenkins-core (maven) versions < 2.462.3 is affected.
4. Is there a fix for CVE-2024-47804? Yes. CVE-2024-47804 is fixed in 2.462.3, 2.479. Upgrade to this version or later.
5. Is CVE-2024-47804 exploitable, and should I be worried? Whether CVE-2024-47804 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-47804 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-47804?
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.462.3 or later
   • Upgrade org.jenkins-ci.main:jenkins-core to 2.479 or later

Other vulnerabilities in org.jenkins-ci.main:jenkins-core