# CVE-2025-24316: Information disclosure in Dario Application Database and Internet-based Server Infrastructure

> Attackers can access sensitive development environment details from the Dario Health server infrastructure, potentially enabling further attacks on the blood glucose monitoring system.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Feb 2025
- **Updated:** 28 Feb 2025
- **Also known as:** GHSA-85x2-vg3f-pxwm

## What is CVE-2025-24316?

CVE-2025-24316 is a medium-severity vulnerability in Dario Application Database and Internet-based Server Infrastructure, published on 28 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Dario Health Internet-based server infrastructure is vulnerable due to exposure of development environment details, which could lead to unsafe functionality.

Weakness: CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies)

## Which versions are affected by CVE-2025-24316?


## How do I fix CVE-2025-24316?

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

## Is CVE-2025-24316 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24316 and fix it if it is affected.

What it is: CVE-2025-24316 is a medium-severity vulnerability in Dario Application Database and Internet-based Server Infrastructure, published on 28 Feb 2025. 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-2025-24316 in the wild and no public exploit code.

Affected product: Dario Application Database and Internet-based Server Infrastructure. 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-2025-24316/ (Markdown: https://insights.sbomify.com/CVE-2025-24316/index.md)
```

## Sources

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

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