CVE-2002-1975

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory (severity: LOW) published 2022-04-30. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Sharp Zaurus PDA SL-5000D and SL-5500 uses a salt of "A0" to encrypt the screen-locking password as stored in the Security.conf file, which makes it easier for local users to guess the password via brute force methods.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
14.7%
KEV
Not listed

Published

December 31, 2002

Last Modified

June 16, 2026

Weakness Classification(1)

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

Frequently asked(5)

What is CVE-2002-1975?
CVE-2002-1975 is a medium vulnerability published on December 31, 2002. Sharp Zaurus PDA SL-5000D and SL-5500 uses a salt of "A0" to encrypt the screen-locking password as stored in the Security.conf file, which makes it easier for local users to guess the password via brute force methods.
When was CVE-2002-1975 disclosed?
CVE-2002-1975 was first published in the National Vulnerability Database on December 31, 2002, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2002-1975 actively exploited?
CVE-2002-1975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2002-1975?
CVE-2002-1975 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2002-1975?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-1975, 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

Explore the affected products and dependency analysis for CVE-2002-1975

Explore →

Is Your Infrastructure Affected by CVE-2002-1975?

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