CVE-2022-45142 — Improper Validation of Integrity Check Value in Project Heimdal
Severity
7.5HIGHNVD
CNA6.5OSV6.5
EPSS
0.1%
top 74.83%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
Timeline
PublishedMar 6
Latest updateMar 14
Description
The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result of memcmp. When these patches were backported to the heimdal-7.7.1 and heimdal-7.8.0 branches (and possibly other branches) a logic inversion sneaked in causing the validation of message integrity codes in gssapi/arcfour to be inverted.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:NExploitability: 3.9 | Impact: 3.6
Affected Packages3 packages
🔴Vulnerability Details
3GHSA▶
GHSA-5gp7-pf54-xc33: The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result↗2023-03-07
CVEList▶
CVE-2022-45142: The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result↗2023-03-06
OSV▶
CVE-2022-45142: The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result↗2023-03-06
📋Vendor Advisories
4Microsoft▶
The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result of memcmp. When these patches were backported to t↗2023-03-14
Debian▶
CVE-2022-45142: heimdal - The fix for CVE-2022-3437 included changing memcmp to be constant time and a wor...↗2022