{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2021-27501 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-27501 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-27501 is a high-severity vulnerability in Philips Vue Motion, published on 1 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-27501 and fix it if it is affected.\n\nWhat it is: CVE-2021-27501 is a high-severity vulnerability in Philips Vue Motion, published on 1 Apr 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-27501 in the wild and no public exploit code.\n\nAffected product: Philips Vue Motion. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-27501/ (Markdown: https://insights.sbomify.com/CVE-2021-27501/index.md)","id":"CVE-2021-27501","markdown":"https://insights.sbomify.com/CVE-2021-27501/index.md","name":"CVE-2021-27501","record":{"aliases":["GHSA-8jv2-wpq7-9vmq"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Medical imaging software","requires_auth":"none","summary":"Philips Vue PACS fails to adhere to coding standards, potentially increasing the severity of other vulnerabilities in the medical imaging system.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"icscert","cpe":[{"product":"myvue","vendor":"philips"},{"product":"speech","vendor":"philips"},{"product":"vue_motion","vendor":"philips"},{"product":"vue_pacs","vendor":"philips"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-710","name":"Improper Adherence to Coding Standards"}],"description":"Philips Vue PACS versions 12.2.x.x and prior does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Philips Vue PACS Improper Adherence to Coding Standards","id":"CVE-2021-27501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Texas Instruments TI-RTOS Integer Overflow or Wraparound","id":"CVE-2021-27502"},"packages":[],"prev":{"headline":"EIPStackGroup OpENer Ethernet/IP Reachable Assertion","id":"CVE-2021-27500"},"products":["Vue Motion","Vue MyVue","Vue PACS","Vue Speech"],"published":"2022-04-01","related":[{"cvss_score":8.2,"headline":"Philips Vue PACS Use of a Key Past its Expiration Date","id":"CVE-2021-33020","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":7.5,"headline":"Philips Vue PACS Use of a Broken or Risky Cryptographic Algorithm","id":"CVE-2021-33018","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":7.5,"headline":"Philips Vue PACS Cleartext Transmission of Sensitive Information","id":"CVE-2021-33022","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2021-39369","kev_date_added":null,"published":"2022-12-26"},{"cvss_score":6.5,"headline":"Philips Vue PACS Protection Mechanism Failure","id":"CVE-2021-27497","kev_date_added":null,"published":"2022-04-01"},{"cvss_score":6.1,"headline":"Philips Vue PACS","id":"CVE-2021-27493","kev_date_added":null,"published":"2022-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-16","vendors":["Philips"]},"summary":"Philips Vue PACS fails to adhere to coding standards, potentially increasing the severity of other vulnerabilities in the medical imaging system.","url":"https://insights.sbomify.com/CVE-2021-27501/"}