What is the CVSS score of CVE-2022-36669?

CVE-2022-36669 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 2.1%.

Is there a public PoC exploit available for CVE-2022-36669?

Yes, a public proof-of-concept exploit is available for CVE-2022-36669. Prioritise patching immediately. EPSS: 2.1%.

Hospital Information System CVE-2022-36669

CRITICAL

SQL Injection (CWE-89)

2022-09-14 cve@mitre.org

Authentication Bypass SQLi Hospital Information System

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Sep 14, 2022 - 11:15 nvd

CRITICAL 9.8

DescriptionNVD

Hospital Information System version 1.0 suffers from a remote SQL injection vulnerability that allows for authentication bypass.

AnalysisAI

Hospital Information System version 1.0 suffers from a remote SQL injection vulnerability that allows for authentication bypass. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as SQL Injection (CWE-89), which allows attackers to execute arbitrary SQL commands against the database. Hospital Information System version 1.0 suffers from a remote SQL injection vulnerability that allows for authentication bypass. Affected products include: Hospital Information System Project Hospital Information System. Version information: version 1.0.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Use parameterized queries/prepared statements. Never concatenate user input into SQL. Apply least-privilege database permissions.