# CVE-2021-29133: Path traversal in n/a

> Local attackers can read arbitrary files on the filesystem due to missing verification in haserl, affecting Alpine Linux systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 24 Mar 2021
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2021-29133, GHSA-55p6-pg28-3hh3, openSUSE-SU-2021:1279-1, openSUSE-SU-2024:10840-1

## What is CVE-2021-29133?

CVE-2021-29133 is a medium-severity path traversal vulnerability in n/a, published on 24 Mar 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Lack of verification in haserl, a component of Alpine Linux Configuration Framework, before 0.9.36 allows local users to read the contents of any file on the filesystem.

## Which versions are affected by CVE-2021-29133?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `haserl` | SUSE:Package Hub 15 SP1 | All versions | 0.9.36-bp153.2.3.1 |
| `haserl` | SUSE:Package Hub 15 SP2 | All versions | 0.9.36-bp153.2.3.1 |
| `haserl` | SUSE:Package Hub 15 SP3 | All versions | 0.9.36-bp153.2.3.1 |
| `haserl` | openSUSE:Leap 15.2 | All versions | 0.9.36-bp153.2.3.1 |
| `haserl` | openSUSE:Leap 15.3 | All versions | 0.9.36-bp153.2.3.1 |
| `haserl` | openSUSE:Tumbleweed | All versions | 0.9.36-1.3 |

Products: Haserl Project Haserl.

## How do I fix CVE-2021-29133?

Upgrade to a fixed version.

## Is CVE-2021-29133 being exploited?

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

Public exploit code:

- Haserl Arbitrary File Reader (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29133 and fix it if it is affected.

What it is: CVE-2021-29133 is a medium-severity path traversal vulnerability in n/a, published on 24 Mar 2021. 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-2021-29133 exists.

Affected product: n/a. 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-2021-29133/ (Markdown: https://insights.sbomify.com/CVE-2021-29133/index.md)
```

## Sources

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

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