dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-34067

CRITICAL · 10.0 CVSS v4.0 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An unauthenticated remote command execution vulnerability exists in the applyCT component of the Hikvision Integrated Security Management Platform due to the use of a vulnerable version of the Fastjson library. The endpoint /bic/ssoService/v1/applyCT deserializes untrusted user input, allowing an attacker to trigger Fastjson's auto-type feature to load arbitrary Java classes. By referencing a malicious class via an LDAP URL, an attacker can achieve remote code execution on the underlying system. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-05 UTC.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unauthenticated remote command execution vulnerability exists in the Hikvision Integrated Security Management Platform's applyCT component at endpoint /bic/ssoService/v1/applyCT. The endpoint deserializes untrusted user input using a vulnerable Fastjson library, enabling attackers to exploit the auto-type feature by referencing malicious Java classes via LDAP URLs, achieving full RCE on the underlying system.

MitigationImmediately restrict network access to the affected endpoint and apply the vendor-supplied patch for the Fastjson vulnerability or upgrade to a patched Hikvision platform version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hikvision ISMP installation
    Search for Hikvision Integrated Security Management Platform processes or check for installation directories such as /opt/hikvision/ or C:\Program Files\Hikvision\ on the server.
    Affected if The platform is installed on the system.
  2. Determine the installed platform version
    Check the platform version by looking for version files in the installation directory, or query the web interface login page for version information if available.
    Affected if The installed version falls within the affected range and has not been patched.
  3. Verify endpoint accessibility
    Attempt to reach the endpoint /bic/ssoService/v1/applyCT from a trusted internal network location using curl or a similar HTTP client: curl -k https://TARGET/bic/ssoService/v1/applyCT
    Affected if The endpoint responds (even with an error), indicating it is exposed and potentially exploitable.
  4. Check Fastjson auto-type status
    Inspect the application configuration files in the platform installation directory for Fastjson settings. Look for files containing 'autotype' or 'autoTypeSupport' configuration.
    Affected if Fastjson auto-type support is enabled (set to true), which is required for the exploit to work.
  5. Review network exposure
    Check firewall rules, reverse proxy configurations, or WAF settings to determine if the /bic/ssoService/v1/applyCT endpoint is accessible from untrusted networks.
    Affected if The endpoint is accessible from outside the trusted network without authentication.

A system is affected if Hikvision ISMP is installed with a vulnerable Fastjson version, the /bic/ssoService/v1/applyCT endpoint is exposed, and Fastjson auto-type support is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict network access to the affected endpoint and apply the vendor-supplied patch for the Fastjson vulnerability or upgrade to a patched Hikvision platform version.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34067 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data