CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.3$0-$5k0.00

Summaryinfo

A vulnerability classified as critical has been found in axTLS 1.5.3. This affects an unknown part of the component ASN.1 Parser. This manipulation of the argument UTCTime causes Remote Code Execution. The identification of this vulnerability is CVE-2017-1000416. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in axTLS 1.5.3 and classified as critical. Affected by this vulnerability is some unknown processing of the component ASN.1 Parser. The manipulation of the argument UTCTime with an unknown input leads to a code vulnerability. The CWE definition for the vulnerability is CWE-17. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 01/22/2018. The weakness was shared 01/22/2018 (Website). It is possible to read the advisory at ieee-security.org. This vulnerability is known as CVE-2017-1000416 since 01/22/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entry VDB-111536 is related to this item. Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.3
VulDB Meta Temp Score: 6.3

VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Code
CWE: CWE-17
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

01/22/2018 🔍
01/22/2018 +0 days 🔍
01/22/2018 +0 days 🔍
01/22/2018 +0 days 🔍
01/23/2018 +1 days 🔍
12/26/2019 +702 days 🔍

Sourcesinfo

Advisory: ieee-security.org
Status: Not defined

CVE: CVE-2017-1000416 (🔍)
GCVE (CVE): GCVE-0-2017-1000416
GCVE (VulDB): GCVE-100-112279
See also: 🔍

Entryinfo

Created: 01/23/2018 07:58
Updated: 12/26/2019 15:36
Changes: 01/23/2018 07:58 (56), 12/26/2019 15:36 (1)
Complete: 🔍
Cache ID: 216::103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Might our Artificial Intelligence support you?

Check our Alexa App!