CVE-2024-58274
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 · uneditedHikvision CSMP (Comprehensive Security Management Platform) iSecure Center through 2024-08-01 allows execution of a command within $( ) in /center/api/installation/detection JSON data, as exploited in the wild in 2024 and 2025.
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 · moderate confidenceHikvision iSecure Center contains a command injection vulnerability in the /center/api/installation/detection endpoint. Attackers can execute arbitrary commands by embedding shell commands within $( ) syntax in JSON data sent to this endpoint. The vulnerability has been actively exploited in the wild during 2024-2025.
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
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Hikvision iSecure Center installationCheck for iSecure Center application files, services, or web interface. Look for processes named 'iSecureCenter' or access the web portal on common ports (80, 443, 8080).Affected if Hikvision iSecure Center software is present on the system
-
Verify the vulnerable endpoint is exposedAttempt to access or probe the URL path /center/api/installation/detection via HTTP/HTTPS. Use a tool like curl: curl -k https://<target>/center/api/installation/detectionAffected if The endpoint responds with any HTTP status (even 404 or 403 indicates the endpoint exists) and is network-accessible
-
Check installed version against available patchesLocate the iSecure Center version information - typically found in the web interface footer, an 'About' page, or in installation logs. Common paths: C:\Program Files\Hikvision\iSecure Center\ or /opt/hikvision/isc/Affected if The installed version is older than the patched version released by Hikvision for this CVE (compare against vendor release notes)
-
Inspect network access controlsReview firewall rules, WAF configurations, or network segmentation that may restrict access to the /center/api/installation/detection endpoint. Check if the endpoint is exposed to untrusted networks.Affected if The endpoint is accessible from untrusted networks without authentication or IP restrictions
-
Review application logs for exploitation indicatorsSearch application and web server logs for requests to /center/api/installation/detection containing suspicious patterns like $(, $(:, `, or other command substitution syntax.Affected if Logs show requests with $( ) syntax or similar command injection patterns to this endpoint
The environment is affected if Hikvision iSecure Center is installed, the /center/api/installation/detection endpoint is accessible, and the installed version predates the vendor patch release date.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-provided patches for iSecure Center; if no patch is available, restrict network access to the /center/api/installation/detection endpoint and implement input validation to sanitize $( ) command substitution syntax from user-supplied JSON data.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-58274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-58274 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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