# CVE-2025-2028: Lack of TLS validation

> Attackers can intercept or modify country mapping data during log server updates due to missing TLS validation, potentially affecting log display integrity.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-7xh6-6qc2-cp9f

## What is CVE-2025-2028?

CVE-2025-2028 is a medium-severity vulnerability in checkpoint Check Point Management Log Server, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lack of TLS validation when downloading a CSV file including mapping from IPs to countries used ONLY for displaying country flags in logs

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Checkpoint Log Server.

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

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

## Is CVE-2025-2028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2028 is a medium-severity vulnerability in checkpoint Check Point Management Log Server, published on 6 Aug 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-2028 in the wild and no public exploit code.

Affected product: checkpoint Check Point Management Log Server. 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-2028/ (Markdown: https://insights.sbomify.com/CVE-2025-2028/index.md)
```

## Sources

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

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