CVE-2018-1000423
First published: Wed Jan 09 2019(Updated: )
An insufficiently protected credentials vulnerability exists in Jenkins Crowd 2 Integration Plugin 2.0.0 and earlier in CrowdSecurityRealm.java, CrowdConfigurationService.java that allows attackers with local file system access to obtain the credentials used to connect to Crowd 2.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Crowd | <=2.0.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-1000423?
CVE-2018-1000423 is rated as a medium severity vulnerability due to its ability to expose credentials.
How do I fix CVE-2018-1000423?
To fix CVE-2018-1000423, upgrade to a version of the Jenkins Crowd 2 Integration Plugin later than 2.0.0.
What is affected by CVE-2018-1000423?
CVE-2018-1000423 affects Jenkins Crowd 2 Integration Plugin version 2.0.0 and earlier.
What are the implications of CVE-2018-1000423?
The implications of CVE-2018-1000423 include potential unauthorized access to credentials used for connecting to Crowd 2.
Who is impacted by CVE-2018-1000423?
Organizations using the vulnerable versions of Jenkins Crowd 2 Integration Plugin are at risk due to CVE-2018-1000423.
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/author
- agent/last-modified-date
- agent/severity
- agent/event
- agent/first-publish-date
- agent/description
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/atlassian
- canonical/atlassian crowd
- version/atlassian crowd/2.0.0