CVE-2018-1000193: Injection in Jenkins
Summary
CVE-2018-1000193: Injection in Jenkins. Affects org.jenkins-ci.main:jenkins-core across 2 version ranges.
< 2.107.3
>= 2.108, < 2.121
Fixed in 2.107.3 or 2.121, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Jenkins is an open-source automation server that allows developers to build, test, and deploy their software projects. It is widely used for continuous integration and delivery. The vulnerable package in question is 'org.jenkins-ci.main:jenkins-core', which is a core component of Jenkins responsible for its main functionality.
Vulnerability Detail
The vulnerability, identified as CVE-2018-1000193, is an injection vulnerability that exists in Jenkins versions 2.120 and older, as well as LTS 2.107.2 and older. The specific vulnerability is present in the 'HudsonPrivateSecurityRealm.java' file. It allows users to sign up using usernames containing control characters, which can then appear to have the same name as other users. These malicious usernames cannot be deleted via the user interface, leading to potential confusion and security risks.
How To Fix
Latest published version: 2.587 as of 22 Oct 2026
Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.
If you can't move to the latest
The minimum fixed version depends on the release line you run.
-
< 2.107.32.107.3 -
>= 2.108, < 2.1212.121
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring that only trusted users are allowed to sign up and by regularly monitoring and reviewing the user accounts in Jenkins.
Conclusion
In conclusion, the CVE-2018-1000193 vulnerability in Jenkins allows users to create usernames with control characters, leading to potential confusion and security risks. It is recommended to upgrade to the fixed versions mentioned earlier to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for org.jenkins-ci.main:jenkins-core →
FAQ
The vulnerability allows users to create usernames with control characters, leading to potential confusion and security risks. It can be used to impersonate other users and cause unauthorized actions within the Jenkins system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins installation is affected by this vulnerability. Simply provide your 'pom.xml' file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
There are no known public exploits for this vulnerability at the time of this report. However, it is always recommended to patch vulnerabilities promptly to prevent any potential exploitation.
Yes, this vulnerability can be exploited remotely. An attacker can create a malicious username with control characters and use it to impersonate other users, potentially gaining unauthorized access to the Jenkins system.
There is no evidence of active attacks exploiting this vulnerability at the time of this report. However, it is crucial to patch the vulnerability to prevent any potential future attacks.
Related vulnerabilities
Recent vulnerabilities recorded for org.jenkins-ci.main:jenkins-core.
