🛡️ AZL-7096 — hivex
Description
CVE-2021-3622 affecting package hivex for versions less than 1.3.21-1
A flaw was found in the hivex library. This flaw allows an attacker to input a specially crafted Windows Registry (hive) file, which would cause hivex to recursively call the _get_children() function, leading to a stack overflow. The highest threat from this vulnerability is to system availability.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability low.
Affected software
AZL-7096 is recorded against 1 package.
- hivex (fixed in 1.3.21-1)
Timeline and source
Published on 23 December 2021 and last revised on 21 April 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| hivex | — | 1.3.21-1 |
References
Similar Threats
- Unknown ALSA-2026:5578
- Unknown ALSA-2025:12527
- Unknown CLSA-2025-1738170241
- Unknown CLSA-2025-1738170437
- Unknown ALSA-2024:6964
More AZL 7 advisories
Browse all of AZL 7 in the advisory index.
Free Vulnerability Check
Is your site affected by AZL-7096?
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against AZL-7096 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.