CVE-2016-9299: Critical severity Jenkins Jenkins vulnerability
The remoting module in Jenkins before 2.32 and LTS before 2.19.3 allows remote attackers to execute arbitrary code via a crafted serialized Java object, which triggers an LDAP query to a third-party server.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.19.3 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.32
Event History
Frequently Asked Questions
What is the severity of CVE-2016-9299?
CVE-2016-9299 is considered a critical vulnerability due to its potential to allow remote code execution.
How do I fix CVE-2016-9299?
To mitigate CVE-2016-9299, upgrade Jenkins to version 2.32 or later, or to LTS version 2.19.3 or later.
What versions of Jenkins are affected by CVE-2016-9299?
CVE-2016-9299 affects Jenkins versions prior to 2.32 and LTS versions prior to 2.19.3.
Can CVE-2016-9299 be exploited remotely?
Yes, CVE-2016-9299 can be exploited remotely by attackers using crafted serialized Java objects.
What impact does CVE-2016-9299 have on my Jenkins installation?
Exploitation of CVE-2016-9299 can lead to arbitrary code execution on the server where Jenkins is running.