CVE-2020-35534

In LibRaw, there is a memory corruption vulnerability within the "crxFreeSubbandData()" function (libraw\src\decoders\crx.cpp) when processing cr3 files.

Published: 2022-09-01 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-35534 is rated Low Risk (27.6/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.25%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-35534

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.06% 0.25% +0.19%
2 2026-05-26 0.15% 0.06% -0.10%
3 2025-11-21 — 0.15% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-35534

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2020-35534

OS Trackers for CVE-2020-35534

vendor priority summary link
alpine medium CVE-2020-35534: 1 source package rows (libraw); 11 state rows across 7 repos (3.17-community, 3.18-community, 3.19-community, 3.20-community, 3.21-community, 3.22-community, edge-community); fixed 11, open 0. https://security.alpinelinux.org/vuln/CVE-2020-35534
debian not yet assigned CVE-2020-35534 not yet assigned priority: Debian including 1 source packages (libraw), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-35534
redhat low — https://access.redhat.com/security/cve/CVE-2020-35534
suse medium — https://www.suse.com/security/cve/CVE-2020-35534/
ubuntu medium CVE-2020-35534 medium priority: Ubuntu including 9 source packages (darktable, dcraw, …), 117 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 46, DNE 28, needs-triage 22, not-affected 19, released 2. https://ubuntu.com/security/CVE-2020-35534

Affected software / configurations for CVE-2020-35534

Vendor Product Version Raw CPE
libraw libraw 0.20.0 cpe:2.3:a:libraw:libraw:0.20.0:-:*:*:*:*:*:*
libraw libraw 0.20.0 cpe:2.3:a:libraw:libraw:0.20.0:rc2:*:*:*:*:*:*
libraw libraw 0.20.1 cpe:2.3:a:libraw:libraw:0.20.1:*:*:*:*:*:*:*
libraw libraw 0.20.2 cpe:2.3:a:libraw:libraw:0.20.2:*:*:*:*:*:*:*
libraw libraw 0.21.0 cpe:2.3:a:libraw:libraw:0.21.0:beta1:*:*:*:*:*:*

References for CVE-2020-35534

cvelogic Threat Intelligence