# CVE-2024-28872: Incorrect TLS certificate validation can lead to escalated privileges

> Attackers can bypass TLS validation to send malicious commands to monitored services, causing data loss or denial of service.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2024
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-cvcp-p7f2-2rhw

## What is CVE-2024-28872?

CVE-2024-28872 is a high-severity vulnerability in ISC Stork, published on 11 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TLS certificate validation code is flawed. An attacker can obtain a TLS certificate from the Stork server and use it to connect to the Stork agent. Once this connection is established with the valid certificate, the attacker can send malicious commands to a monitored service (Kea or BIND 9), possibly resulting in confidential data loss and/or denial of service. It should be noted that this vulnerability is not related to BIND 9 or Kea directly, and only customers using the Stork management tool are potentially affected.
This issue affects Stork versions 0.15.0 through 1.15.0.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Isc Stork.

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

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

## Is CVE-2024-28872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-28872 is a high-severity vulnerability in ISC Stork, published on 11 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-28872 in the wild and no public exploit code.

Affected product: ISC Stork. 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-28872/ (Markdown: https://insights.sbomify.com/CVE-2024-28872/index.md)
```

## Sources

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

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