# CVE-2024-51163: Path traversal in n/a

> Remote attackers can exploit a Local File Inclusion vulnerability in Vegam 4i to read sensitive server files via the print label function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Nov 2024
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-76ph-jc9g-v47h

## What is CVE-2024-51163?

CVE-2024-51163 is a high-severity path traversal vulnerability in n/a, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Local File Inclusion vulnerability in Vegam Solutions Vegam 4i versions 6.3.47.0 and earlier allows a remote attacker to obtain sensitive information through the print label function. Specifically, the filePathList parameter is susceptible to LFI, enabling a malicious user to include files from the web server, such as web.config or /etc/host, leading to the disclosure of sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-51163?


## How do I fix CVE-2024-51163?

No fix has been published for CVE-2024-51163 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-51163 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51163 and fix it if it is affected.

What it is: CVE-2024-51163 is a high-severity path traversal vulnerability in n/a, published on 20 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51163 in the wild and no public exploit code.

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

## Sources

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

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