CVE-2017-1000416
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedaxTLS 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceaxTLS 1.5.3 contains a coding error in its ASN.1 parser where the two-digit year value '50' in UTCTime is incorrectly interpreted as 2050 instead of 1950. This affects how the library handles certificate validity periods since UTCTime uses a 2-digit year format where values 50-99 represent 1950-1999 and 00-49 represent 2000-2049.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.5.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify axTLS versionLocate the axTLS library or package installed in your environment and query its version information (e.g., check library file metadata, package manager listing, or version string in source files)Affected if The installed version is exactly 1.5.3
-
Confirm SSL/TLS usageDetermine whether your application or service uses axTLS for SSL/TLS connections - check compilation flags, linked libraries, or configuration files that reference axTLSAffected if axTLS is used for SSL/TLS functionality
-
Verify certificate validation pathInspect whether your code calls functions that validate certificate validity periods (e.g., x509_cert_verify) - this is where the UTCTime parsing vulnerability is triggeredAffected if Certificate validity period validation is performed using the vulnerable axTLS code
-
Check for UTCTime certificate handlingReview any certificates in use that contain validity periods encoded in UTCTime format (2-digit year), particularly those expiring in years 1950-1999Affected if Certificates with validity periods using UTCTime format (years 50-99 in the 2-digit encoding) are being processed
You are affected if axTLS version 1.5.3 is installed and your system uses it to validate certificates containing UTCTime-encoded validity periods where the 2-digit year falls in the 50-99 range (representing 1950-1999).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade axTLS to a version that corrects the ASN.1 UTCTime year parsing logic, or patch the parser to correctly handle years 50-99 as 1950-1999.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,432.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000416 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1000416 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data