LiveActive security incident?Get immediate response
CVE Record

CVE-2022-45207: Jeecg-boot v3.4.3 was discovered to contain a SQL injection vulnerability via the component updateNullByEmp...

Jeecg-boot v3.4.3 was discovered to contain a SQL injection vulnerability via the component updateNullByEmptyString.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-45207 is a critical SQL injection issue reported in Jeecg-boot v3.4.3. In business terms, a vulnerable exposed deployment could let an unauthenticated attacker affect database confidentiality, integrity, and availability. The source bundle does not name a fixed version or confirmed active exploitation.

Executive priority

Treat as urgent for any confirmed Jeecg-boot v3.4.3 deployment, particularly internet-facing systems. The high CVSS score reflects potential database compromise, but remediation planning should acknowledge that the supplied sources do not confirm active exploitation or a fixed release.

Technical view

The CVE describes SQL injection in Jeecg-boot v3.4.3 through the updateNullByEmptyString component. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Organizations most likely exposed are those running Jeecg-boot v3.4.3, especially internet-facing or partner-facing instances that reach application database functions. The CVE record lacks structured CPE data, so product inventory and code ownership checks are required.

Exploitation context

The bundle marks CISA KEV status as false, and no provided source confirms active exploitation. The CVSS vector indicates exploitation is theoretically remote and unauthenticated, but the bundle does not provide endpoint details or exploit evidence.

Researcher notes

Evidence is thin beyond the CVE description and linked GitHub issue. The affected product is named in text, but the structured affected and CPE fields are not useful. Validate reachability and fixed-version status from upstream before making exploitability claims.

Mitigation direction

  • Identify any Jeecg-boot v3.4.3 deployments or forks in production and staging.
  • Review the upstream GitHub issue and vendor guidance for fixed versions or official mitigation.
  • Prioritize upgrade or remediation once an official fix path is confirmed.
  • Limit external access to affected application surfaces until remediation is complete.
  • Review database account permissions used by the application for unnecessary privileges.

Validation and detection

  • Confirm application versions through deployment manifests, package metadata, and runtime inventory.
  • Check whether updateNullByEmptyString exists in the deployed code path.
  • Determine whether affected functionality is reachable without authentication in your deployment.
  • Review application and database logs for unusual SQL errors or unexpected data changes.
  • After remediation, run regression tests around affected database update behavior.
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-2022-45207 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.8 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

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.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-45207Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
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.