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

> Attackers can intercept sensitive data via man-in-the-middle attacks because mmudb uses unencrypted HTTP for metrics functions.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 31 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-2wxr-xh8w-9rjx

## What is CVE-2024-41262?

CVE-2024-41262 is a high-severity vulnerability in n/a, published on 31 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mmudb v1.9.3 was discovered to use the HTTP protocol in the ShowMetricsRaw and ShowMetricsAsText functions, possibly allowing attackers to intercept communications via a man-in-the-middle attack.

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

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

It affects 1 product.


Products: Codenotary Immudb.

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

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

## Is CVE-2024-41262 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-39199](https://insights.sbomify.com/CVE-2022-39199/): Lack of proper validation in immudb (medium 5.8)
- [CVE-2022-36111](https://insights.sbomify.com/CVE-2022-36111/): immundb has insufficient verification of data authenticity (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41262 is a high-severity vulnerability in n/a, published on 31 Jul 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-41262 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-41262/ (Markdown: https://insights.sbomify.com/CVE-2024-41262/index.md)
```

## Sources

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

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