# CVE-2023-30571: Race condition in n/a

> A race condition in Libarchive can set directory permissions to world-writable, allowing local users to modify or delete files.

- **Severity:** Low 3.9 (`CVSS:3.1/AC:H/AV:L/A:N/C:L/I:L/PR:L/S:C/UI:R`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 May 2023
- **Updated:** 14 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-30571, GHSA-cw7x-3mv7-w6xm, JLSEC-2025-238, UBUNTU-CVE-2023-30571

## What is CVE-2023-30571?

CVE-2023-30571 is a low-severity vulnerability in Libarchive Libarchive, published on 29 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2023-30571?

It affects 1 product.


Products: Libarchive Libarchive.

## How do I fix CVE-2023-30571?

Apply the vendor's patch.

## Is CVE-2023-30571 being exploited?

There is no known exploitation of CVE-2023-30571 in the wild and no public exploit code.

## Other vulnerabilities in Libarchive Libarchive

- [CVE-2024-37407](https://insights.sbomify.com/CVE-2024-37407/): Memory corruption in n/a (critical 9.1)
- [CVE-2016-1541](https://insights.sbomify.com/CVE-2016-1541/): Memory corruption in n/a (high 8.8)
- [CVE-2016-6250](https://insights.sbomify.com/CVE-2016-6250/): Integer overflow in n/a (high 8.6)
- [CVE-2025-5914](https://insights.sbomify.com/CVE-2025-5914/): Libarchive: double free at archive_read_format_rar_seek_data() in archive_read_support_format_rar.c (high 7.8)
- [CVE-2024-48957](https://insights.sbomify.com/CVE-2024-48957/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30571 and fix it if it is affected.

What it is: CVE-2023-30571 is a low-severity vulnerability in Libarchive Libarchive, published on 29 May 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-30571 in the wild and no public exploit code.

Affected product: Libarchive Libarchive. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-30571/ (Markdown: https://insights.sbomify.com/CVE-2023-30571/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-30571
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-30571
- OSV: https://osv.dev/vulnerability/CVE-2023-30571

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-30571/
Summaries are generated and may contain mistakes; the official description above is the record.