LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43362: MedData HBYS 1.0 Remote SQL Injection Vulnerability

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in MedData HBYS allows SQL Injection.This issue affects HBYS: from unspecified before 1.1.

CriticalCVSS 9.9Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

MedData HBYS versions before 1.1 have a critical remotely reachable SQL injection issue. An unauthenticated attacker could manipulate database queries, risking sensitive data exposure and some integrity or availability impact. The provided sources do not show CISA KEV listing or confirmed active exploitation.

Executive priority

Treat this as high-priority if HBYS is deployed, because unauthenticated network SQL injection can threaten sensitive healthcare and operational records. Urgency is lower only if no affected HBYS instance exists or exposure is tightly controlled.

Technical view

CVE-2021-43362 is CWE-89 in MedData HBYS before 1.1. CVSS 3.1 is 9.9 with network access, low complexity, no privileges, no user interaction, changed scope, high confidentiality impact, and low integrity and availability impact.

Likely exposure

Exposure is limited to organizations running MedData HBYS versions earlier than 1.1, especially internet-reachable deployments. The source bundle does not identify CPEs, deployment patterns, or specific vulnerable endpoints.

Exploitation context

The CVE reference includes a public gist, but the bundle does not provide verified exploitation details here. CISA KEV is false, so active exploitation should not be asserted from these sources alone.

Researcher notes

Evidence is sparse beyond the CVE record, CVSS vector, affected range before 1.1, CWE-89 classification, and a public gist reference. Do not assume endpoint details, exploit maturity, or vendor patch mechanics without additional vendor confirmation.

Mitigation direction

  • Inventory MedData HBYS deployments and identify versions below 1.1.
  • Prioritize upgrade to HBYS 1.1 or later if supported by MedData guidance.
  • Restrict external access to HBYS until remediation is confirmed.
  • Review vendor advisories or support channels for official fixes and hardening guidance.
  • Monitor database and application logs for suspicious query errors or unusual access patterns.

Validation and detection

  • Confirm HBYS version from application or asset records.
  • Verify whether HBYS is reachable from untrusted networks.
  • Check compensating controls such as WAF rules and network ACLs.
  • Review logs for SQL errors, abnormal requests, or unexpected database activity.
  • Document remediation status and retest after upgrade or access restriction.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-43362 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.9CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L3.95.3Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.9Critical
CVSS 3.1 vector shape for CVE-2021-43362Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MedDataHBYSunspecifiedunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.