# CVE-2024-41700: Barix – CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

> An attacker can access sensitive information from the Barix SIP Client Web Management Interface without authorization.

- **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 Aug 2024
- **Updated:** 21 Aug 2024
- **Also known as:** GHSA-g467-xxq2-x845

## What is CVE-2024-41700?

CVE-2024-41700 is a high-severity vulnerability in Barix SIP Client Web Management Interface UI, published on 20 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Barix – CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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

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

It affects 1 product.


Products: Barix Sip Client Firmware.

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

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

## Is CVE-2024-41700 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41700 is a high-severity vulnerability in Barix SIP Client Web Management Interface UI, published on 20 Aug 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-41700 in the wild and no public exploit code.

Affected product: Barix SIP Client Web Management Interface UI. 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-41700/ (Markdown: https://insights.sbomify.com/CVE-2024-41700/index.md)
```

## Sources

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

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