# CVE-2025-4384: Certificate validity not properly verified

> Attackers can bypass certificate validation in PcVue's MQTT add-on by presenting expired or not-yet-valid certificates, allowing unauthorized device connections.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/AU:N/R:U/RE:M/U:Green`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2025
- **Updated:** 5 Sep 2025
- **Also known as:** GHSA-2wpp-x4cq-cp8g

## What is CVE-2025-4384?

CVE-2025-4384 is a medium-severity vulnerability in arcinfo PcVue, published on 6 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The MQTT add-on of PcVue fails to verify that a remote device’s certificate has not already expired or has not yet become valid. This allows malicious devices to present certificates that are not rejected properly.

The use of a client certificate reduces the risk for random devices to take advantage of this flaw.

Weakness: CWE-298 (Improper Validation of Certificate Expiration)

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


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

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

## Is CVE-2025-4384 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4384 is a medium-severity vulnerability in arcinfo PcVue, published on 6 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4384 in the wild and no public exploit code.

Affected product: arcinfo PcVue. 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-4384/ (Markdown: https://insights.sbomify.com/CVE-2025-4384/index.md)
```

## Sources

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

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