CVE-2024-14007
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 · uneditedShenzhen TVT Digital Technology Co., Ltd. NVMS-9000 firmware (used by many white-labeled DVR/NVR/IPC products) versions prior to 1.3.4 contain an authentication bypass in the NVMS-9000 control protocol. By sending a single crafted TCP payload to an exposed NVMS-9000 control port, an unauthenticated remote attacker can invoke privileged administrative query commands without valid credentials. Successful exploitation discloses sensitive information including administrator usernames and passwords in cleartext, network and service configuration, and other device details via commands such as queryBasicCfg, queryUserList, queryEmailCfg, queryPPPoECfg, and queryFTPCfg.
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 confidenceAuthentication bypass in NVMS-9000 firmware allows unauthenticated remote attackers to send crafted TCP packets to the control port and invoke privileged administrative query commands (queryBasicCfg, queryUserList, queryEmailCfg, queryPPPoECfg, queryFTPCfg) without credentials, exposing administrator usernames and passwords in cleartext plus network/service configuration.
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:N/VA:N/SC:N/SI:N/SA:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NVMS-9000 software presenceLocate the NVMS-9000 application or service on the target system. This is typically deployed as a video management system on Windows servers. Check for processes named 'NVMS9000.exe' or look for the software in program directories.Affected if NVMS-9000 software is found installed on the system
-
Determine NVMS-9000 firmware versionAccess the NVMS-9000 admin interface or check system information within the application. The firmware version is typically displayed in the system info or about section of the management console. Compare the installed version against the fixed version 1.3.4.Affected if Installed version is earlier than 1.3.4
-
Verify control port exposureScan the system or network device for open TCP port 34567 using a port scanner (e.g., 'nmap -p 34567 <target>') or check firewall rules and network access control lists for inbound allow rules on this port.Affected if TCP port 34567 is open and accessible from untrusted networks
-
Confirm authentication bypass vulnerabilitySend a raw TCP packet containing one of the vulnerable query commands (e.g., 'queryUserList') to port 34567 using a tool like netcat or a custom script, and observe if the device returns sensitive configuration data without requiring authentication.Affected if The device responds with sensitive data (usernames, passwords, configuration) without any authentication credentials
The environment is affected if NVMS-9000 firmware version is below 1.3.4 AND TCP port 34567 is accessible from the network, allowing unauthenticated command execution.
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.
dbcve · scopedUpgrade to firmware version 1.3.4 or later where available; for unsupported devices, segment the network and block access to the NVMS-9000 control port (typically TCP 34567) from untrusted networks using firewalls or VPC security groups.
NVMS-9000 firmware version 1.3.4
- Identify all NVMS-9000 devices (DVR/NVR/IPC) on the network that may be running affected firmware
- Contact Shenzhen TVT Digital Technology Co., Ltd. or your device vendor to obtain the official firmware version 1.3.4 or later
- Review vendor release notes and upgrade documentation for any specific upgrade prerequisites or procedures
- Backup current device configuration before initiating firmware update
- Upgrade each affected device's firmware to version 1.3.4 or later via the vendor-provided update mechanism
- After upgrade, verify that the authentication bypass is remediated by confirming that unauthenticated queries to the control port no longer return sensitive data
- Validate that normal administrative functions still work correctly with valid credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-14007 — 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-14007 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