CVE-2020-16237

LOWNVD 2.12.1—

2.1

Philips SureSigns VS4, A.07.107 and prior receives input or data, but it does not validate or incorrectly validates that the input has the properties required to process the data safely and correctly.

CVSS v3: 2.1
EG Score: 2.1(medium)
EPSS: 15.1%
KEV: Not listed

Published

August 21, 2020

Last Modified

June 4, 2025

References (3)

ics-cert@hqhttps://us-cert.cisa.gov/ics/advisories/icsma-20-233-01
ics-cert@hqhttps://www.philips.com/a-w/security/security-advisories/product-security-2020.html#2020_archive
af854a3a-2127-422b-91ae-364da2661108https://us-cert.cisa.gov/ics/advisories/icsma-20-233-01

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-20Improper Input Validation

Data Freshness Timeline

(refreshed 12× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

2026-06-08 14:15 UTCEPSS rescore
2026-06-08 14:15 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-06 13:45 UTCEPSS rescore
2026-06-05 22:45 UTCEPSS rescore
2026-06-05 22:45 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-04 13:10 UTCEPSS rescore
2026-06-04 13:10 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 00:15 UTCEPSS rescore
2026-05-31 00:15 UTCEPSS rescore
2026-05-29 13:42 UTCEPSS rescore
2026-05-28 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2020-16237?

CVE-2020-16237 is a low vulnerability published on August 21, 2020. Philips SureSigns VS4, A.07.107 and prior receives input or data, but it does not validate or incorrectly validates that the input has the properties required to process the data safely and correctly.

When was CVE-2020-16237 disclosed?

CVE-2020-16237 was first published in the National Vulnerability Database on August 21, 2020, with the most recent update on June 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-16237 actively exploited?

CVE-2020-16237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 15.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-16237?

CVE-2020-16237 has a CVSS v3 base score of 2.1 (NVD).

How do I remediate CVE-2020-16237?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-16237, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-16237

Explore →

Is Your Infrastructure Affected by CVE-2020-16237?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-16237

📅 Published

🔄 Last Modified

🔗 References (3)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-16237?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (3)

Frequently asked(5)

Related CVEs(same CWE)