Vulnerability in Tp Link Omada Oc200 V3 Firmware (CVE-2025-15628, CVSS 7.5)

Summary

Vulnerability in Tp Link Omada Oc200 V3 Firmware (CVE-2025-15628). Confidential information can be exposed externally.

Original description

The description as published by the source.

Affected
Omada devices rely on embedded certificates that are shared across deployments
to establish trust between controllers and managed devices.

An attacker
who obtains the embedded certificates may be able to impersonate trusted
controllers or devices and intercept affected communications.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2025-15628 has been found in Tp Link Omada Oc200 V3 Firmware.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Tp Link Omada Oc200 V3 Firmware CVE-2025-15628" on the vendor's site.

CVE-2025-15628 (Tp Link Omada Oc200 V3 Firmware) — CWE-798 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-798) exists in Tp Link Omada Oc200 V3 Firmware.

📍 Affected scope

Check the vendor advisory for the affected versions of Tp Link Omada Oc200 V3 Firmware.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Tp Link Omada Oc200 V3 Firmware を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Summary

Original description

Auto-generated summary

Response actions

References