dbcve.org
Hikcentral MasterApplication · Hikvision

CVE-2024-47485

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-18
Fix available
A fix is available. Upgrade to 2.3.0 or later.
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
There is a CSV injection vulnerability in some HikCentral Master Lite versions. If exploited, an attacker could build malicious data to generate executable commands in the CSV file.

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 confidence

A CSV injection vulnerability exists in HikCentral Master Lite where malicious data can be crafted to embed executable commands (formulae) into CSV export files. When users open these CSV files in spreadsheet applications, the embedded formulas can be executed, potentially allowing arbitrary command execution on the victim's machine.

MitigationImplement strict input validation and output encoding for all data exported to CSV, specifically sanitizing or rejecting special characters (=, +, -, @, tab, CR) at the beginning of data fields, and consider adding warning banners in generated CSV files.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hikcentral MasterApplication
Affected:>= 2.0.0, < 2.3.0

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed HikCentral Master version
    Locate the HikCentral Master installation and check its version number, typically found in the application UI under About/Help or in the installation directory metadata
    Affected if Installed version is >= 2.0.0 and < 2.3.0
  2. Confirm CSV export functionality is accessible
    Determine whether the CSV export feature is available and enabled in the HikCentral Master installation (check admin console or feature settings)
    Affected if CSV export feature is present and accessible to users
  3. Review recent CSV export operations
    Examine the system for any CSV files generated by HikCentral Master, particularly in export/download directories or recent user activity logs
    Affected if CSV exports exist that may contain unvalidated user-supplied data in fields
  4. Inspect CSV file contents for formula injection patterns
    Open or parse any exported CSV files and examine whether fields begin with special characters (=, +, -, @, tab, CR) which indicate potential formula injection payloads
    Affected if Exported CSV files contain fields starting with formula characters (=, +, -, @)

You are affected if HikCentral Master version 2.0.0 through 2.2.x is installed and CSV export functionality has been used to generate files from user-controlled or external data sources.

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.

dbcve · scoped
Upgrade available Upgrade to 2.3.0 or later
Fixed in 2.3.0
Interim mitigation

Implement strict input validation and output encoding for all data exported to CSV, specifically sanitizing or rejecting special characters (=, +, -, @, tab, CR) at the beginning of data fields, and consider adding warning banners in generated CSV files.

Recommended fix Moderate confidence

2.3.0 or later

  1. 1. Identify the current Hikcentral Master version installed in your environment
  2. 2. Download Hikcentral Master version 2.3.0 or later from the official Hikvision website (www.hikvision.com)
  3. 3. Review release notes for version 2.3.0 to understand changes and any migration requirements
  4. 4. Create a full backup of the current Hikcentral Master configuration and database
  5. 5. Schedule a maintenance window for the upgrade process
  6. 6. Stop all Hikcentral Master services before beginning the upgrade
  7. 7. Install Hikcentral Master version 2.3.0 or newer following the official installation guide
  8. 8. Verify the upgrade was successful by checking the version number in the system information

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Hikcentral Master Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-47485 — 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-2024-47485 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