dbcve.org
Video Management Systems FirmwareOperating system · Milesight

CVE-2022-3001

HIGH · 7.5 CVSS v3.1 Published 2022-09-15
Fix available
A fix is available. Upgrade to 40.7.0.79 or later.
See remediation →
84/100
Remediation priority · High
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
This vulnerability exists in Milesight Video Management Systems (VMS), all firmware versions prior to 40.7.0.79-r1, due to improper input handling at camera’s web-based management interface. A remote attacker could exploit this vulnerability by sending a specially crafted http request on the targeted network camera. Successful exploitation of this vulnerability could allow the attacker to cause a Denial of Service condition on the targeted device.

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

Milesight VMS cameras running firmware versions prior to 40.7.0.79-r1 contain an improper input handling vulnerability in their web-based management interface. A remote attacker can send a specially crafted HTTP request to trigger the flaw, causing a Denial of Service condition on the targeted camera device.

MitigationUpdate Milesight camera firmware to version 40.7.0.79-r1 or later. If immediate patching is not feasible, restrict network access to the camera management interfaces using firewall rules or VLAN segmentation.

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
Video Management Systems FirmwareOperating system
Affected:< 40.7.0.79= 40.7.0.79

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the device as a Milesight VMS camera
    Locate the physical camera or access your network device inventory to confirm the device model is a Milesight camera product. Check the device label, packaging, or network scan results for the Milesight manufacturer.
    Affected if The device is not a Milesight VMS camera product, then this CVE does not apply.
  2. Access the web-based management interface
    Open a web browser and navigate to the camera's IP address. Log in with administrator credentials to access the management dashboard.
    Affected if The web management interface is not accessible or not configured, then the attack surface for this vulnerability may be limited.
  3. Locate the firmware version information
    In the web interface, navigate to System or Maintenance settings (often under System > Maintenance > Version or Device Info). Record the displayed firmware version number.
    Affected if The firmware version cannot be retrieved from the web interface, check the physical device label or use the Milesight discovery tool / ONVIF to query the firmware version.
  4. Compare firmware version against affected range
    Compare the installed firmware version to the affected versions: any version less than 40.7.0.79, or exactly version 40.7.0.79. The fixed version is 40.7.0.79-r1 or later.
    Affected if Installed firmware version is < 40.7.0.79 OR installed version equals exactly 40.7.0.79, then the device is affected by this vulnerability.

If the Milesight VMS camera runs firmware version 40.7.0.79 or any earlier version (but not 40.7.0.79-r1 or later), and the web-based management interface is network-accessible, the environment is affected by CVE-2022-3001.

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 40.7.0.79 or later
Fixed in 40.7.0.79
Interim mitigation

Update Milesight camera firmware to version 40.7.0.79-r1 or later. If immediate patching is not feasible, restrict network access to the camera management interfaces using firewall rules or VLAN segmentation.

Recommended fix High confidence

40.7.0.79-r1

  1. Check current firmware version of the Milesight VMS/network camera device
  2. Download firmware version 40.7.0.79-r1 (or later) from the official Milesight support website or portal
  3. Access the camera's web-based management interface
  4. Navigate to the firmware upgrade section (typically under System > Maintenance or similar)
  5. Upload and apply the downloaded firmware file
  6. Wait for the upgrade process to complete and the device to reboot
  7. Verify the new firmware version is 40.7.0.79-r1 or higher
  8. Confirm the device is functioning normally and the web interface is accessible

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

Fix this in Video Management Systems Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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