Read the docs
TI-2018-09627 Aliases CVE-2018-13390GHSA-4fpg-j5mp-783g

Insufficiently protected credentials in Atlassian cloudtoken

Priority LOW 28CWE-522Published · Updated

Key facts

Attack vector
Adjacent network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Information disclosure
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA and GitHub. Impact type from CWE-522.

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.

Why it matters now

EPSS 0.00463 40th percentileScored 2026-11-07
Fix Fixed cloudtoken (Atlassian): 0.1.24cloudtoken (PyPI): 0.1.24

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
Atlassiancloudtoken0.1.1 and later; before 0.1.240.1.24Patch availableCNA
—cloudtoken (PyPI)0.1.1 to before 0.1.240.1.24Patch availableGHSA-4fpg-j5mp-783g
  • cloudtoken VendorAtlassian Affected 0.1.1 and later; before 0.1.24 Fixed in 0.1.24 Patch available CNA
  • cloudtoken (PyPI) Vendor— Affected 0.1.1 to before 0.1.24 Fixed in 0.1.24 Patch available GHSA-4fpg-j5mp-783g

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:atlassian:cloudtoken:*:*:*:*:*:*:*:*0.1.1 to before 0.1.24VulnerableAtlassian
  • cpe:2.3:a:atlassian:cloudtoken:*:*:*:*:*:*:*:* Versions 0.1.1 to before 0.1.24 Vulnerable ·Atlassian

Remediation

  • Fix · CNA cloudtoken (Atlassian) Fixed in 0.1.24
  • Fix · GHSA-4fpg-j5mp-783g cloudtoken (PyPI) Fixed in 0.1.24 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2018-13390
  2. 2026-10-03 Alias added: GHSA-4fpg-j5mp-783g

References

Sources