dbcve.org
Vmb3010 FirmwareOperating system · Arlo

CVE-2019-3949

CRITICAL · 9.8 CVSS v3.0 Published 2019-07-09
Fix available
A fix is available. Upgrade to 1.12.2.2_2824 / 1.12.2.3_2762 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
Arlo Basestation firmware 1.12.0.1_27940 and prior firmware contain a networking misconfiguration that allows access to restricted network interfaces. This could allow an attacker to upload or download arbitrary files and possibly execute malicious code on the 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 · moderate confidence

Arlo Basestation firmware versions 1.12.0.1_27940 and prior contain a networking misconfiguration that exposes restricted network interfaces to unauthorized attackers. This allows remote attackers to upload or download arbitrary files to/from the device, potentially leading to arbitrary code execution.

MitigationUpdate Arlo Basestation firmware to a patched version beyond 1.12.0.1_27940. If immediate patching is not possible, implement network segmentation to restrict access to the device and monitor for unauthorized access attempts.

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
Vmb3010 FirmwareOperating system
Affected:< 1.12.2.3_2762
Vmb4000 FirmwareOperating system
Affected:< 1.12.2.3_2762
Vmb3500 FirmwareOperating system
Affected:< 1.12.2.4_2773
Vmb4500 FirmwareOperating system
Affected:< 1.12.2.4_2773
Vmb5000 FirmwareOperating system
Affected:< 1.12.2.2_2824

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.0/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 Arlo Basestation model number
    Locate the model number on the physical device label or check the device list in the Arlo web interface or mobile app under device settings
    Affected if Model is Vmb3010, Vmb4000, Vmb3500, Vmb4500, or Vmb5000
  2. Check installed firmware version
    In the Arlo interface, navigate to Settings > My Devices > select the basestation > click Device Info to view the firmware version
    Affected if Firmware version cannot be verified or is displayed as unknown
  3. Compare firmware version against affected ranges
    Compare your installed firmware version to the affected ranges: Vmb3010/Vmb4000 if < 1.12.2.3_2762; Vmb3500/Vmb4500 if < 1.12.2.4_2773; Vmb5000 if < 1.12.2.2_2824
    Affected if Installed version falls below the corresponding threshold for your model

You are affected if you have an Arlo basestation model Vmb3010, Vmb4000, Vmb3500, Vmb4500, or Vmb5000 running firmware below the patched version threshold for your specific model.

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 1.12.2.2_2824 / 1.12.2.3_2762 / 1.12.2.4_2773 or later
Fixed in 1.12.2.2_28241.12.2.3_27621.12.2.4_2773
Interim mitigation

Update Arlo Basestation firmware to a patched version beyond 1.12.0.1_27940. If immediate patching is not possible, implement network segmentation to restrict access to the device and monitor for unauthorized access attempts.

Recommended fix High confidence

Vmb3010/Vmb4000: firmware >= 1.12.2.3_2762 | Vmb3500/Vmb4500: firmware >= 1.12.2.4_2773 | Vmb5000: firmware >= 1.12.2.2_2824

  1. Identify the exact Vmb model number (Vmb3010, Vmb4000, Vmb3500, Vmb4500, or Vmb5000) of the Arlo BaseStation
  2. Access the Arlo web portal or mobile application to check the current firmware version
  3. Navigate to the device settings and check for firmware updates, or visit kb.arlo.com for manual firmware download
  4. For Vmb3010 and Vmb4000: Update firmware to version 1.12.2.3_2762 or later
  5. For Vmb3500 and Vmb4500: Update firmware to version 1.12.2.4_2773 or later
  6. For Vmb5000: Update firmware to version 1.12.2.2_2824 or later
  7. Verify the firmware update was successful by checking the firmware version in device settings
  8. Restart the BaseStation to ensure the new firmware is fully applied
Caveat None identified - firmware update is a patch for a networking misconfiguration vulnerability

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

Fix this in Vmb3010 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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