CVE-2002-0176

NONECVSS 0.0

0.0

The printf wrappers in libsafe 2.0-11 and earlier do not properly handle argument indexing specifiers, which could allow attackers to exploit certain function calls through arguments that are not verified by libsafe.

CVSS v3: —
EG Score: —
EPSS: 36.5%
KEV: Not listed

Published

April 22, 2002

Last Modified

April 16, 2026

References (10)

cve@mitrehttp://archives.neohapsis.com/archives/vulnwatch/2002-q1/0070.html
cve@mitrehttp://online.securityfocus.com/archive/1/263121
cve@mitrehttp://www.iss.net/security_center/static/8594.php
cve@mitrehttp://www.linux-mandrake.com/en/security/2002/MDKSA-2002-026.php
cve@mitrehttp://www.securityfocus.com/bid/4327
af854a3a-2127-422b-91ae-364da2661108http://archives.neohapsis.com/archives/vulnwatch/2002-q1/0070.html
af854a3a-2127-422b-91ae-364da2661108http://online.securityfocus.com/archive/1/263121
af854a3a-2127-422b-91ae-364da2661108http://www.iss.net/security_center/static/8594.php
af854a3a-2127-422b-91ae-364da2661108http://www.linux-mandrake.com/en/security/2002/MDKSA-2002-026.php
af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/4327

Data Freshness Timeline

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

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-29 13:40 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-27 13:37 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 13:41 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-26 07:16 UTCepss_batch
2026-05-24 16:42 UTCepss_batch
2026-05-22 21:15 UTCepss_batch
2026-05-21 22:38 UTCepss_batch
2026-05-20 22:36 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-20 11:20 UTCepss_batch
2026-05-18 21:29 UTCepss_batch
2026-05-18 21:29 UTCepss_batch

Frequently asked(4)

What is CVE-2002-0176?

CVE-2002-0176 is a none vulnerability published on April 22, 2002. The printf wrappers in libsafe 2.0-11 and earlier do not properly handle argument indexing specifiers, which could allow attackers to exploit certain function calls through arguments that are not verified by libsafe.

When was CVE-2002-0176 disclosed?

CVE-2002-0176 was first published in the National Vulnerability Database on April 22, 2002, with the most recent update on April 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-0176 actively exploited?

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

How do I remediate CVE-2002-0176?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2002-0176, 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-2002-0176

Explore →

Is Your Infrastructure Affected by CVE-2002-0176?

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

Start Free Scan →Browse All CVEs

CVE-2002-0176

📅 Published

🔄 Last Modified

🔗 References (10)