# CVE-2024-48121: Information disclosure in n/a

> Attackers can intercept cleartext credentials via man-in-the-middle attacks on the HI-SCAN 6040i Hitrax HX-03-19-I, potentially gaining unauthorized access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jan 2025
- **Updated:** 3 Feb 2025
- **Also known as:** GHSA-4cxr-9fjv-2m3m

## What is CVE-2024-48121?

CVE-2024-48121 is a medium-severity vulnerability in n/a, published on 15 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The HI-SCAN 6040i Hitrax HX-03-19-I was discovered to transmit user credentials in cleartext over the GIOP protocol. This allows attackers to possibly gain access to sensitive information via a man-in-the-middle attack.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2024-48121 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48121 is a medium-severity vulnerability in n/a, published on 15 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48121 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-2024-48121/ (Markdown: https://insights.sbomify.com/CVE-2024-48121/index.md)
```

## Sources

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

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