CVE-2023-1384
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 · uneditedThe setMediaSource function on the amzn.thin.pl service does not sanitize the "source" parameter allowing for arbitrary javascript code to be run This issue affects: Amazon Fire TV Stick 3rd gen versions prior to 6.2.9.5. Insignia TV with FireOS versions prior to 7.6.3.3.
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 confidenceA cross-site scripting (XSS) vulnerability exists in the setMediaSource function on the amzn.thin.pl service used by Amazon Fire TV devices. The 'source' parameter is not properly sanitized, allowing an attacker to inject and execute arbitrary JavaScript code in the context of the application.
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< 6.2.9.5< 7.6.3.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify the Fire TV device modelLocate the device model number in Settings > My Fire TV > About on the Amazon Fire TV deviceAffected if Device is a Fire TV Stick 3rd gen or Insignia FireOS TV model
-
Check the installed Fire OS versionNavigate to Settings > My Fire TV > About and note the Fire OS version number displayedAffected if Version is below 6.2.9.5 for Fire TV Stick 3rd gen, or below 7.6.3.3 for Insignia FireOS TVs
-
Verify network exposure of amzn.thin.pl serviceInspect network traffic or DNS records for queries to the amzn.thin.pl domain from the Fire TV deviceAffected if The device makes requests to amzn.thin.pl and the Fire OS version is in the affected range
The device is affected if it runs Fire OS versions below 6.2.9.5 (Fire TV Stick 3rd gen) or below 7.6.3.3 (Insignia FireOS TVs) and communicates with the amzn.thin.pl service.
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 · scoped6.2.9.57.6.3.3
Update Amazon Fire TV Stick 3rd gen to version 6.2.9.5 or later, and Insignia FireOS TVs to version 7.6.3.3 or later to remediate this vulnerability.
Fire TV Stick 3rd gen: 6.2.9.5 or higher; Insignia TV with FireOS: 7.6.3.3 or higher
- On your Fire TV or Insignia TV with FireOS, navigate to Settings
- Select 'My Fire TV' or 'Device'
- Choose 'About'
- Select 'Check for Updates' or 'Software Version'
- If an update is available, select 'Download' and then 'Install'
- Alternatively, ensure automatic updates are enabled by going to Settings > My Fire TV > About > Automatic Updates and enable it
- Wait for the update to complete and verify the version is at least 6.2.9.5 (Fire TV Stick 3rd gen) or 7.6.3.3 (Insignia TV with FireOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1384 — 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-2023-1384 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