Home/CVE/In JetBrains Kotlin before 1.4.21, a vulnerable Java API was used for temporary file and folder creation. An attacker wa
CVE
CVE-2020-2958215
In JetBrains Kotlin before 1.4.21, a vulnerable Java API was used for temporary file and folder creation. An attacker wa
In JetBrains Kotlin before 1.4.21, a vulnerable Java API was used for temporary file and folder creation. An attacker was able to read data from such files and list directories due to insecure permissions.
MEDIUM · CVSS 5.3
EPSS 0.02572
EPSS exploitation odds2.57% · top 16%
Schedule remediation
- Public exploit or PoC is available
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2020-29582, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
⚠
Exploitation evidence
1 of 7 sources
Corroboration score 8/100 ·
emerging.
This counts how many independent sources have exploitation evidence, and separates two different things:
confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from
exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means
an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC
↗
Exploitation momentum
41 days of EPSSdormant
Flat and low - no real exploitation pressure. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
EPSS exploitation probability
2.57%
Top 16%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NLifecycle
- 03 Feb 2021Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
⚠
Public Exploits & PoCs
15These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
Source
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
Works?
no reports yet
Rating
◆
ATT&CK techniques
2Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
3Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
▤
Affected Products & Versions
4▤
Affected Packages
1Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.
Maven
org.jetbrains.kotlin:kotlin-stdlib
MODERATE
fixed in 1.4.21
▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row.
CVE-1999-0426
The default permissions of /dev/kmem in Linux versions before 2.0.36 allows IP s...
1
same CWE-276
CRITICAL
CVE-2001-0497
dnskeygen in BIND 8.2.4 and earlier, and dnssec-keygen in BIND 9.1.2 and earlier...
same CWE-276
HIGH
CVE-2002-1713
The Standard security setting for Mandrake-Security package (msec) in Mandrake 8...
same CWE-276
MEDIUM
CVE-2002-1844
Microsoft Windows Media Player (WMP) 6.3, when installed on Solaris, installs ex...
same CWE-276
HIGH
CVE-2019-10101
JetBrains Kotlin versions before 1.3.30 were resolving artifacts using an http c...
same product
HIGH
CVE-2019-10102
JetBrains Ktor framework (created using the Kotlin IDE template) versions before...
same product
HIGH
CVE-2019-10103
JetBrains IntelliJ IDEA projects created using the Kotlin (JS Client/JVM Server)...
same product
HIGH
CVE-2022-24329
In JetBrains Kotlin before 1.6.0, it was not possible to lock dependencies for M...
same product
MEDIUM
⚑
Vendor Advisories
3🔗
References & Sources
6Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.