Jianming Antivirus 16.2.2022.418 IoControlCode kvcore.sys null pointer dereference

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.
5.3$0-$5k0.71

Summaryinfo

A vulnerability labeled as problematic has been found in Jianming Antivirus 16.2.2022.418. The affected element is an unknown function in the library kvcore.sys of the component IoControlCode Handler. The manipulation results in null pointer dereference. This vulnerability is known as CVE-2023-1628. Attacking locally is a requirement. Furthermore, an exploit is available.

Detailsinfo

A vulnerability classified as problematic has been found in Jianming Antivirus 16.2.2022.418 (Anti-Malware Software). Affected is an unknown part in the library kvcore.sys of the component IoControlCode Handler. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability.

The weakness was published 03/25/2023. The advisory is available at github.com. This vulnerability is traded as CVE-2023-1628. Technical details and a public exploit are known.

The exploit is shared for download at drive.google.com. It is declared as proof-of-concept.

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍

CNA Base Score: 5.5
CNA Vector (VulDB): 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

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

03/25/2023 🔍
03/25/2023 +0 days 🔍
03/25/2023 +0 days 🔍
04/15/2023 +21 days 🔍

Sourcesinfo

Advisory: github.com
Status: Not defined

CVE: CVE-2023-1628 (🔍)
GCVE (CVE): GCVE-0-2023-1628
GCVE (VulDB): GCVE-100-224010
scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 03/25/2023 11:11
Updated: 04/15/2023 09:53
Changes: 03/25/2023 11:11 (42), 04/15/2023 09:49 (2), 04/15/2023 09:53 (27)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!