CVE-2022-43591 json
A buffer overflow vulnerability exists in the QML QtScript Reflect API of Qt Project Qt 6.3.2.
published 3y ago modified 4mo ago also EUVD-2022-46587
- cvss
- 8.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 67%
- public exploits
- 0
- none known
Summary
A buffer overflow vulnerability exists in the QML QtScript Reflect API of Qt Project Qt 6.3.2. A specially-crafted javascript code can trigger an out-of-bounds memory access, which can lead to arbitrary code execution. Target application would need to access a malicious web page to trigger this vulnerability.
Patch / fix
- qt6-declarative Debian 14, Debian 13, Debian 12 6.4.2+dfsg~rc1-2
debian advisories DEBIAN-CVE-2022-43591
Is CVE-2022-43591 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 FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
1.18% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2022-1650 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Qt Project Qt
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
talosintelligence.com
/vulnerability_reports/TALOS-2022-1650
exploit, third-party-advisory
- talosintelligence.com /vulnerability_reports/TALOS-2022-1650
Sources
- CVE List CVE-2022-43591
- NVD CVE-2022-43591
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.