# CVE-2023-32698: nfpm vulnerable to Incorrect Default Permissions

> nfpm fails to preserve file permissions, potentially exposing sensitive files with world-readable or writable permissions in generated packages.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2023
- **Updated:** 10 Jan 2025
- **Also known as:** GHSA-w7jw-q4fg-qc4c, GO-2023-1788

## What is CVE-2023-32698?

CVE-2023-32698 is a high-severity vulnerability in goreleaser nfpm, published on 30 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

nFPM is an alternative to fpm. The file permissions on the checked-in files were not maintained. Hence, when nfpm packaged 
the files (without extra config for enforcing it’s own permissions) files could go out with bad permissions (chmod 666 or 777). Anyone using nfpm for creating packages without checking/setting file permissions before packaging could result in bad permissions for files/folders.

Weakness: CWE-276 (Incorrect Default Permissions)

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

5 open source packages ship an affected version, including github.com/goreleaser/nfpm/v2 and github.com/goreleaser/nfpm. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/goreleaser/nfpm/v2` | Go | From 2.0.0 | 2.29.0 |
| `github.com/goreleaser/nfpm/v2` | Go | From 2.0.0 | 2.29.0 |
| `github.com/goreleaser/nfpm/v2` | Go | From 2.0.0 | 2.29.0 |
| `github.com/goreleaser/nfpm` | Go | From 0.1.0 to 1.10.3 | None |
| `github.com/goreleaser/nfpm` | Go | From 0.1.0 to 1.10.3 | None |

Products: Goreleaser Nfpm.

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

Upgrade github.com/goreleaser/nfpm/v2 to 2.29.0 or later.

## Is CVE-2023-32698 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32698 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-32698 is a high-severity vulnerability in goreleaser nfpm, published on 30 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32698 exists.

Affected packages and fixed versions:
- github.com/goreleaser/nfpm/v2 (Go): affected from 2.0.0; fixed in 2.29.0
- github.com/goreleaser/nfpm/v2 (Go): affected from 2.0.0; fixed in 2.29.0
- github.com/goreleaser/nfpm/v2 (Go): affected from 2.0.0; fixed in 2.29.0
- github.com/goreleaser/nfpm (Go): affected from 0.1.0 up to 1.10.3; no fix listed
- github.com/goreleaser/nfpm (Go): affected from 0.1.0 up to 1.10.3; no fix listed

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-32698/ (Markdown: https://insights.sbomify.com/CVE-2023-32698/index.md)
```

## Sources

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

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