cve.bz

CVE-2023-1630 jiangmin jiangmin antivirus: Improper Resource Shutdown or Release

5.5 mediumExploit referenceEPSS 0.3%

Medium (5.5) in jiangmin jiangmin antivirus. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
A vulnerability, which was classified as problematic, has been found in JiangMin Antivirus 16.2.2022.418. Affected by this issue is the function 0x222000 in the library kvcore.sys of the component IOCTL Handler. The manipulation leads to denial of service. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-224012.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-404 Improper Resource Shutdown or Release
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2023-1630 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-1630?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-1630?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-1630 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
jiangmin:jiangmin_antivirus16.2.2022.418

Attack patterns (CAPEC)

  • CAPEC-125 Flooding Likelihood: High · Severity: Medium
  • CAPEC-130 Excessive Allocation Likelihood: Medium · Severity: Medium
  • CAPEC-131 Resource Leak Exposure Likelihood: Medium · Severity: Medium
  • CAPEC-494 TCP Fragmentation
  • CAPEC-495 UDP Fragmentation
  • CAPEC-496 ICMP Fragmentation
  • CAPEC-666 BlueSmacking Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON