CVE-2021-3941: In ImfChromaticities.cpp routine RGBtoXYZ(), there are some division operations such as `float Z = (1 - chroma.white.x - chroma.white.y) * Y
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: openexr (Debian:11) 2.5.4-2+deb11u1; openexr (Debian:12) 3.1.5-2; openexr (openSUSE:Leap 15.2) 2.2.1-lp152.7.23.1.
Low priority for now. Upgrade to openexr (Debian:11) 2.5.4-2+deb11u1; openexr (Debian:12) 3.1.5-2; openexr (openSUSE:Leap 15.2) 2.2.1-lp152.7.23.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In ImfChromaticities.cpp routine RGBtoXYZ(), there are some division operations such as `float Z = (1 - chroma.white.x - chroma.white.y) * Y / chroma.white.y;` and `chroma.green.y * (X + Z))) / d;` but the divisor is not checked for a 0 value. A specially crafted file could trigger a divide-by-zero condition which could affect the availability of programs linked with OpenEXR.
- Published
- Mar 25, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 23th percentile
- CWE
- CWE-369
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openexr | openexr | cpe:2.3:a:openexr:openexr |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux11.0
- fedoraproject fedora34
- fedoraproject fedora35
- fedoraproject fedora36
- openexr openexr3.1.2
- redhat enterprise linux6.0
- redhat enterprise linux7.0
- redhat enterprise linux8.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a openexr
- OpenEXR 3.1.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | openexr | before 2.5.4-2+deb11u1 | 2.5.4-2+deb11u1 |
| Debian:12 | openexr | before 3.1.5-2 | 3.1.5-2 |
| openSUSE:Leap 15.2 | openexr | before 2.2.1-lp152.7.23.1 | 2.2.1-lp152.7.23.1 |
| openSUSE:Leap 15.3 | openexr | before 2.2.1-3.38.1 | 2.2.1-3.38.1 |
| SUSE:Linux Enterprise Module for Desktop Applications 15 SP2 | openexr | before 2.2.1-3.38.1 | 2.2.1-3.38.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | OpenEXR | before 1.6.1-83.17.30.1 | 1.6.1-83.17.30.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | openexr | before 2.1.0-6.42.1 | 2.1.0-6.42.1 |
Same product
openexr: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-5841OpenEXR Heap Overflow in Scanline Deep Data Parsing36Monitor
- CVE-2021-23169A heap-buffer overflow was found in the copyIntoFrameBuffer function of OpenEXR in versions before 3.0.1.36Monitor
- CVE-2017-9115In OpenEXR 2.2.0, an invalid write of size 2 in the = operator function in half.h could cause the application to crash or execute arbitrary 36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-20299Mar 16, 2022 · A flaw was found in OpenEXR's Multipart input file functionality.31Monitor
- ← EarlierCVE-2021-3933Mar 25, 2022 · An integer overflow could occur when OpenEXR processes a crafted file on systems where size_t < 64 bits.22Monitor
- Later →CVE-2021-20298Aug 23, 2022 · A flaw was found in OpenEXR's B44Compressor.30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:openexr | 3.1.5-2 · Debian:12 | Package registry (OSV) |
| opensuse:openexr | 2.2.1-lp152.7.23.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| suse:openexr | 2.1.0-6.42.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:OpenEXR | 1.6.1-83.17.30.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-369 · Divide By ZeroCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.