CVE-2021-39369
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 · uneditedIn Philips (formerly Carestream) Vue MyVue PACS through 12.2.x.x, the VideoStream function allows Path Traversal by authenticated users to access files stored outside of the web root.
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 confidenceThis is an authenticated path traversal vulnerability in the VideoStream function of Philips Vue MyVue PACS. An authenticated attacker can manipulate file path inputs to escape the web root directory and access sensitive files on the underlying file system.
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 dataall versionsall versions<= 12.2.1.5all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Philips PACS productInventory your systems for Philips Vue MyVue, Philips Speech, Philips Vue Motion, or Philips Vue PACS software installationsAffected if Any of these products are installed and the VideoStream function is accessible without additional hardening
-
Check Philips Vue Motion versionIf Philips Vue Motion is installed, query its installed version number and compare to 12.2.1.5 (affected if <= 12.2.1.5)Affected if Vue Motion version is 12.2.1.5 or lower
-
Verify VideoStream endpoint exposureInspect web server or application configuration to determine if the VideoStream function is exposed via HTTP/HTTPSAffected if The VideoStream endpoint is reachable over the network
-
Confirm authentication is enforcedTest the VideoStream endpoint with and without valid credentials to verify authentication is requiredAffected if The VideoStream function can be accessed without authentication (authenticated vulnerability but check if auth is actually enforced)
-
Review access logs for traversal attemptsExamine web access logs for requests to the VideoStream function containing path traversal sequences (such as ../ or ..\)Affected if Historical or current logs show exploitation attempts using path traversal in VideoStream requests
Your environment is affected if you have any Philips Vue MyVue, Philips Speech, Philips Vue Motion (version <= 12.2.1.5), or Philips Vue PACS installed with the VideoStream function exposed and accessible, regardless of whether authentication is currently enforced.
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.
From vendor dataImplement strict input validation and path canonicalization in the VideoStream function to ensure all file paths resolve within an allowed directory. Use allowlist validation for file requests and ensure proper path sanitization to prevent traversal sequences (e.g., ../) from accessing files outside the designated web root.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39369 — 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-2021-39369 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