CVE-2019-9483
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 · uneditedAmazon Ring Doorbell before 3.4.7 mishandles encryption, which allows attackers to obtain audio and video data, or insert spoofed video that does not correspond to the actual person at the door.
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 confidenceThe Amazon Ring Doorbell devices before firmware version 3.4.7 contain an encryption mishandling vulnerability that allows attackers to obtain audio and video data through improper cryptographic implementation. Attackers can also inject spoofed video that does not correspond to the actual person at the door, indicating both confidentiality and integrity impacts on the video stream.
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< 3.4.7CVSS 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
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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.
-
Check the installed firmware versionOpen the Ring mobile app, select the Ring Doorbell device, go to Device Settings, then Device Info, and locate the Firmware Version field. Alternatively, access the device through the Ring website and navigate to the device details page.Affected if The displayed firmware version is below 3.4.7 (for example, 3.4.6, 3.3.9, etc.)
-
Check device health statusIn the Ring app, select the doorbell device and tap Device Health to view current status, signal strength, and firmware information.Affected if The firmware version shown in Device Health is less than 3.4.7 or shows as out of date
-
Verify if firmware update is availableIn the Ring app, go to the device settings and check for any pending firmware updates. A device affected by this CVE would typically show an available update to version 3.4.7 or later.Affected if The app indicates a firmware update is available, suggesting the current version is older than the latest patched release
You are affected if your Ring Doorbell is running firmware version 3.4.6 or any version prior to 3.4.7, as these versions contain the encryption mishandling vulnerability that exposes audio and video data.
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 · scoped3.4.7
Update Ring Doorbell firmware to version 3.4.7 or later to remediate the encryption vulnerability; verify that devices are running the patched version and on supported software lifecycles.
Firmware version 3.4.7
- Open the Ring mobile application and navigate to your device settings
- Locate the Ring Video Doorbell device in the device list
- Check the current firmware version under Device Settings or Device Info
- If firmware version is below 3.4.7, select the option to update firmware
- Ensure the doorbell is connected to a stable Wi-Fi network during the update
- Wait for the firmware download and installation to complete - do not disconnect power
- After the update finishes, verify the new firmware version displays 3.4.7 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9483 — 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-2019-9483 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