First published: Wed Mar 25 2015(Updated: )
The HudsonPrivateSecurityRealm class in Jenkins before 1.600 and LTS before 1.596.1 does not restrict access to reserved names when using the "Jenkins' own user database" setting, which allows remote attackers to gain privileges by creating a reserved name.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/Jenkins | <1.600 | 1.600 |
redhat/Jenkins | <1.596.1 | 1.596.1 |
Jenkins | <=1.580.3 | |
Red Hat OpenShift | <=3.1 | |
Jenkins | <=1.599 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-1810 has a medium severity rating due to its potential to allow privilege escalation through reserved names.
To fix CVE-2015-1810, upgrade Jenkins to version 1.600 or later, or LTS to version 1.596.1 or later.
CVE-2015-1810 affects Jenkins versions prior to 1.600 and LTS versions prior to 1.596.1.
Yes, CVE-2015-1810 can be exploited remotely by an attacker to gain unauthorized privileges.
The impact of CVE-2015-1810 is that unauthorized users can create reserved usernames, potentially gaining elevated privileges within Jenkins.