CVE-2017-1000416

MEDIUMNVD 5.3

5.3

axTLS version 1.5.3 has a coding error in the ASN.1 parser resulting in the year (19)50 of UTCTime being misinterpreted as 2050.

CVSS v3: 5.3
EG Score: —
EPSS: 52.8%
KEV: Not listed

Published

January 22, 2018

Last Modified

November 21, 2024

References (4)

cve@mitrehttps://www.ieee-security.org/TC/SP2017/papers/231.pdf
cve@mitrehttps://www.youtube.com/watch?v=FW--c_F_cY8
af854a3a-2127-422b-91ae-364da2661108https://www.ieee-security.org/TC/SP2017/papers/231.pdf
af854a3a-2127-422b-91ae-364da2661108https://www.youtube.com/watch?v=FW--c_F_cY8

Weakness Classification(1)

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

CWE-193Off-by-one Error

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 16:16 UTCOSV refresh
2026-05-24 16:44 UTCepss_batch

Frequently asked(5)

What is CVE-2017-1000416?

CVE-2017-1000416 is a medium vulnerability published on January 22, 2018. axTLS version 1.5.3 has a coding error in the ASN.1 parser resulting in the year (19)50 of UTCTime being misinterpreted as 2050.

When was CVE-2017-1000416 disclosed?

CVE-2017-1000416 was first published in the National Vulnerability Database on January 22, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-1000416 actively exploited?

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

What is the CVSS score of CVE-2017-1000416?

CVE-2017-1000416 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2017-1000416?

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

Explore →

Is Your Infrastructure Affected by CVE-2017-1000416?

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

Start Free Scan →Browse All CVEs

CVE-2017-1000416

📅 Published

🔄 Last Modified

🔗 References (4)