CVE-2022-44638: In libpixman in Pixman before 0.42.2, there is an out-of-bounds write (aka heap-based buffer overflow) in rasterize_edges_8 due to an intege
Noroxi assessment
Priority: Monitor (action score 36/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: 1.9% (FIRST EPSS); higher than 79.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: pixman (AlmaLinux:8) 0.38.4-3.el8_9; pixman-devel (AlmaLinux:8) 0.38.4-3.el8_9; mingw32-pixman (AlmaLinux:9) 0.42.2-3.el9.
Low priority for now. Upgrade to pixman (AlmaLinux:8) 0.38.4-3.el8_9; pixman-devel (AlmaLinux:8) 0.38.4-3.el8_9; mingw32-pixman (AlmaLinux:9) 0.42.2-3.el9 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 libpixman in Pixman before 0.42.2, there is an out-of-bounds write (aka heap-based buffer overflow) in rasterize_edges_8 due to an integer overflow in pixman_sample_floor_y.
- Published
- Nov 3, 2022
- Updated
- Jun 17, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-190
Report tools
Action score
36
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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 |
|---|---|---|
| pixman | pixman | cpe:2.3:a:pixman:pixman |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
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 fedora35
- fedoraproject fedora36
- fedoraproject fedora37
- pixman pixmanbefore 0.42.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | pixman | before 0.38.4-3.el8_9 | 0.38.4-3.el8_9 |
| AlmaLinux:8 | pixman-devel | before 0.38.4-3.el8_9 | 0.38.4-3.el8_9 |
| AlmaLinux:9 | mingw32-pixman | before 0.42.2-3.el9 | 0.42.2-3.el9 |
| AlmaLinux:9 | mingw64-pixman | before 0.42.2-3.el9 | 0.42.2-3.el9 |
| AlmaLinux:9 | pixman | before 0.40.0-6.el9_3 | 0.40.0-6.el9_3 |
| AlmaLinux:9 | pixman-devel | before 0.40.0-6.el9_3 | 0.40.0-6.el9_3 |
| Alpine:v3.13 | pixman | before 0.40.0-r3 | 0.40.0-r3 |
| Alpine:v3.15 | pixman | before 0.40.0-r4 | 0.40.0-r4 |
| Debian:10 | pixman | before 0.36.0-1+deb10u1 | 0.36.0-1+deb10u1 |
| Debian:11 | pixman | before 0.40.0-1.1~deb11u1 | 0.40.0-1.1~deb11u1 |
| Debian:12 | pixman | before 0.40.0-1.1 | 0.40.0-1.1 |
| openSUSE:Leap Micro 5.2 | pixman | before 0.34.0-150000.7.5.1 | 0.34.0-150000.7.5.1 |
| openSUSE:Leap Micro 5.3 | pixman | before 0.40.0-150400.3.3.1 | 0.40.0-150400.3.3.1 |
| Red Hat:enterprise_linux:8::appstream | pixman | before 0:0.38.4-3.el8_9 | 0:0.38.4-3.el8_9 |
| Red Hat:enterprise_linux:8::appstream | pixman-debuginfo | before 0:0.38.4-3.el8_9 | 0:0.38.4-3.el8_9 |
| Red Hat:enterprise_linux:8::appstream | pixman-debugsource | before 0:0.38.4-3.el8_9 | 0:0.38.4-3.el8_9 |
| Red Hat:enterprise_linux:8::appstream | pixman-devel | before 0:0.38.4-3.el8_9 | 0:0.38.4-3.el8_9 |
| Red Hat:enterprise_linux:9::appstream | pixman | before 0:0.40.0-6.el9_3 | 0:0.40.0-6.el9_3 |
| Red Hat:enterprise_linux:9::appstream | pixman-debuginfo | before 0:0.40.0-6.el9_3 | 0:0.40.0-6.el9_3 |
| Red Hat:enterprise_linux:9::appstream | pixman-debugsource | before 0:0.40.0-6.el9_3 | 0:0.40.0-6.el9_3 |
| Red Hat:enterprise_linux:9::appstream | pixman-devel | before 0:0.40.0-6.el9_3 | 0:0.40.0-6.el9_3 |
| Red Hat:enterprise_linux:9::crb | mingw-pixman | before 0:0.42.2-3.el9 | 0:0.42.2-3.el9 |
| Red Hat:enterprise_linux:9::crb | mingw32-pixman | before 0:0.42.2-3.el9 | 0:0.42.2-3.el9 |
| Red Hat:enterprise_linux:9::crb | mingw32-pixman-debuginfo | before 0:0.42.2-3.el9 | 0:0.42.2-3.el9 |
+23
Same product
pixman: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-9766Integer overflow in the create_bits function in pixman-bits-image.c in Pixman before 0.32.6 allows remote attackers to cause a denial of ser41Plan
- CVE-2015-5297An integer overflow issue has been reported in the general_composite_rect() function in pixman prior to version 0.32.8.39Monitor
- CVE-2023-37769stress-test master commit e4c878 was discovered to contain a FPE vulnerability via the component combine_inner at /pixman-combine-float.c.26Monitor
Published before and after this one in the same product
- ← EarlierCVE-2013-6424Jan 18, 2014 · Integer underflow in the xTrapezoidValid macro in render/picture.h in X.Org allows context-dependent attackers to cause a denial of service 21Monitor
- ← EarlierCVE-2013-6425Jan 18, 2014 · Integer underflow in the pixman_trapezoid_valid macro in pixman.h in Pixman before 0.32.0, as used in X.Org server and cairo, allows context21Monitor
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 |
|---|---|---|
| almalinux:mingw32-pixman | 0.42.2-3.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:mingw64-pixman | 0.42.2-3.el9 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:pixman | 0.40.0-6.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:pixman-devel | 0.40.0-6.el9_3 · AlmaLinux:9 | Package registry (OSV) |
| alpine:pixman | 0.40.0-r3 · Alpine:v3.13 | Package registry (OSV) |
| debian:pixman | 0.40.0-1.1 · Debian:12 | Package registry (OSV) |
| opensuse:pixman | 0.34.0-150000.7.5.1 · openSUSE:Leap Micro 5.2 | Package registry (OSV) |
| red hat:mingw-pixman | 0:0.42.2-3.el9 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:mingw32-pixman | 0:0.42.2-3.el9 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:mingw32-pixman-debuginfo | 0:0.42.2-3.el9 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:mingw64-pixman | 0:0.42.2-3.el9 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:mingw64-pixman-debuginfo | 0:0.42.2-3.el9 · Red Hat:enterprise_linux:9::crb | Package registry (OSV) |
| red hat:pixman | 0:0.40.0-6.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:pixman-debuginfo | 0:0.40.0-6.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:pixman-debugsource | 0:0.40.0-6.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:pixman-devel | 0:0.40.0-6.el9_2 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| rocky linux:mingw-pixman | 0:0.42.2-3.el9 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:pixman | 0:0.40.0-6.el9_3 · Rocky Linux:9 | Package registry (OSV) |
| suse:pixman | 0.34.0-150000.7.5.1 · SUSE:Linux Enterprise Module for Basesystem 15 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- lists.debian.org/debian-lts-announce/2022/11/msg00008.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AJ5VY2VYXE4WTRGQ6LMGLF6FV3SY37YE/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BY4OPSIB33ETNUXZY2UPZ4NGQ3OKDY4D/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IUJ2BULJTZ2BMSKQHB6US674P55UCWWS/
- www.debian.org/security/2022/dsa-5276
Vendor advisories and official records. Exploit/PoC links are deliberately left out.