dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-0530

MEDIUM · 5.5 CVSS v3.1 Published 2022-02-09
Fix available
A fix is available. Upgrade to 10.15.7 / 11.6.6 or later.
See remediation →
58/100
Remediation priority · Elevated
Public exploit No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Unzip. The vulnerability occurs during the conversion of a wide string to a local string that leads to a heap of out-of-bound write. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 8.0
FedoraOperating system
Affected:= 35
Debian LinuxOperating system
Affected:= 10.0= 11.0
UnzipApplication
Affected:= 6.0
Mac Os XOperating system
Affected:>= 10.15, < 10.15.7= 10.15.7
macOSOperating system
Affected:>= 11.0, < 11.6.6>= 12.0.0, < 12.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.15.7 / 11.6.6 / 12.4 or later
Fixed in 10.15.711.6.612.4
Recommended fix High confidence

Unzip 6.0-23 or later (or vendor-patched versions via OS update)

  1. 1. Identify the current unzip version installed on the system using: unzip -v or dpkg -l unzip (Debian) / rpm -qa | grep unzip (RHEL)
  2. 2. For Linux distributions (Debian, RHEL, Fedora): Update the package repository and upgrade unzip to the latest available version that includes the security fix
  3. 3. On macOS: Update to macOS 10.15.7 (if on 10.15.x), macOS 11.6.6 (if on 11.x), or macOS 12.4 (if on 12.x) or later to receive the Apple security update for unzip
  4. 4. Verify the vulnerability is patched by running: unzip -v and confirm the version is greater than 6.0
Caveat Minor: Upgrading unzip to newer versions is generally low risk, but verify compatibility with any scripts that depend on specific unzip behavior

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0530 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data