CVE-2018-1000610: A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in DataBoundConfigura
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.89% (FIRST EPSS); higher than 59.7% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: io.jenkins:configuration-as-code (Maven) 0.8-alpha.
Low priority for now. Upgrade to io.jenkins:configuration-as-code (Maven) 0.8-alpha or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in DataBoundConfigurator.java, Attribute.java, BaseConfigurator.java, ExtensionConfigurator.java that allows attackers with access to Jenkins log files to obtain the passwords configured using Configuration as Code Plugin.
- Published
- Jun 26, 2018
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 59th percentile
- CWE
- CWE-522
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jenkins | configuration as code | cpe:2.3:a:jenkins:configuration_as_code |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jenkins configuration as code0.1
- jenkins configuration as code0.2
- jenkins configuration as code0.3
- jenkins configuration as code0.4
- jenkins configuration as code0.5
- jenkins configuration as code0.6
- jenkins configuration as code0.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | io.jenkins:configuration-as-code | before 0.8-alpha | 0.8-alpha |
Same product
jenkins: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-1000609A exposure of sensitive information vulnerability exists in Jenkins Configuration as Code Plugin 0.7-alpha and earlier in ConfigurationAsCod26Monitor
- CVE-2019-10367Due to an incomplete fix of CVE-2019-10343, Jenkins Configuration as Code Plugin 1.26 and earlier did not properly apply masking to some val22Monitor
- CVE-2019-10345Jenkins Configuration as Code Plugin 1.20 and earlier did not treat the proxy password as a secret to be masked when logging or encrypted fo22Monitor
Published before and after this one in the same product
- Later →CVE-2019-10343Jul 31, 2019 · Jenkins Configuration as Code Plugin 1.24 and earlier did not properly apply masking to values expected to be hidden when logging the config13Monitor
- Later →CVE-2019-10344Jul 31, 2019 · Missing permission checks in Jenkins Configuration as Code Plugin 1.24 and earlier in various HTTP endpoints allowed users with Overall/Read17Monitor
- Later →CVE-2019-10362Jul 31, 2019 · Jenkins Configuration as Code Plugin 1.24 and earlier did not escape values resulting in variable interpolation during configuration import 21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:io.jenkins:configuration-as-code | 0.8-alpha | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- Signature Spoofing by Key TheftCAPEC-474likelihood: Medium · High
- Password Recovery ExploitationCAPEC-50likelihood: Medium · High
- KerberoastingCAPEC-509High
- Modify Existing ServiceCAPEC-551
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid AccountsT1078
- Brute Force:Credential StuffingT1110.004
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Create or Modify System ProcessT1543
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Unsecured Credentials: Private KeysT1552.004
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.