Skip to content
Fencer Intel
high 8.8

CVE-2020-15824 json

In JetBrains Kotlin from 1.4-M1 to 1.4-RC (as Kotlin 1.3.7x is not affected by the issue.

published 6y ago modified 4mo ago also EUVD-2020-7806

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

Summary

In JetBrains Kotlin from 1.4-M1 to 1.4-RC (as Kotlin 1.3.7x is not affected by the issue. Fixed version is 1.4.0) there is a script-cache privilege escalation vulnerability due to kotlin-main-kts cached scripts in the system temp directory, which is shared by all users by default.

Patch / fix

Is CVE-2020-15824 in your stack? 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-15824 updated cvss 8.8

kotlin: kotlin-main-kts cached scripts in the system temp directory could result in priviledge escalation

  • Red Hat Fuse 7 camel-k-runtime-kotlin camel-k-runtime-kotlin Red Hat Integration Camel K 1 Kotlin Kotlin, kotlin-stdlib, kotlin-reflect, kotlin-stdlib-jdk7, kotlin-stdlib-jdk8, kotlin-stdlib-common Red Hat Integration Service Registry kotlin-stdlib, kotlin-reflect, kotlin-stdlib-jdk7, kotlin-stdlib-jdk8, kotlin-stdlib-common
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 6.5 AV:N/AC:L/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-269 Improper Privilege Management

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.