Skip to content
Fencer Intel
medium 4.3

CVE-2020-2126 json

Token stored in plain text by DigitalOcean Plugin

published 6y ago modified 4mo ago also GHSA-8g6v-g8qc-5w7j , EUVD-2022-3175

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits
0
none known

Summary

Jenkins DigitalOcean Plugin 1.1 and earlier stores a token unencrypted in the global config.xml file on the Jenkins master where it can be viewed by users with access to the master file system.

Patch / fix

  • maven com.dubture.jenkins:digitalocean-plugin 1.2.0

Is CVE-2020-2126 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:P/I:N/A:N
GitHub 3.0 3.3 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven com.dubture.jenkins:digitalocean-plugin
<1.2.0
1.2.0

Affected products

  • Jenkins project Jenkins DigitalOcean Plugin

Classification

Weakness
  • CWE-522 Insufficiently Protected Credentials
  • CWE-256 Plaintext Storage of a Password

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.