CVE-2018-13390 json
Cloudtoken Insufficiently Protects Credentials
published 8y ago modified 4mo ago also GHSA-4fpg-j5mp-783g , PYSEC-2018-1 , EUVD-2018-0028
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
Unauthenticated access to cloudtoken daemon on Linux via network from version 0.1.1 before version 0.1.24 allows attackers on the same subnet to gain temporary AWS credentials for the users' roles.
Patch / fix
- pypi cloudtoken 0.1.24
- Atlassian cloudtoken 0.1.24
Is CVE-2018-13390 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 FencerExploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 4.8 | AV:A/AC:L/Au:N/C:P/I:P/A:N |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | cloudtoken | >=0.1.1, <0.1.24 |
0.1.24 |
Affected products
- Atlassian cloudtoken
Classification
- Weakness
-
- CWE-522 Insufficiently Protected Credentials
References
-
bitbucket.org
/atlassian/cloudtoken/wiki/CVE-2018-13390%20-%20Exposed%20credentials%20in%20daemon%20mode%20on%20Linux
web, mitigation, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2018-13390
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/cloudtoken/PYSEC-2018-1.yaml
web
-
github.com
/advisories/GHSA-4fpg-j5mp-783g
advisory
Sources
- CVE List CVE-2018-13390
- GitHub Advisory GHSA-4fpg-j5mp-783g
- NVD CVE-2018-13390
- OSV PYSEC-2018-1
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.