LiveActive security incident?Get immediate response
CVE Record

CVE-2023-30445: IBM Db2 denial of service

IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 10.5, 11.1, and 11.5 is vulnerable to denial of service with a specially crafted query on certain tables. IBM X-Force ID: 253357.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Affected IBM Db2 systems can be made unavailable by a specially crafted query against certain tables. The business risk is service outage for applications depending on Db2, not confirmed data theft or data alteration. Treat this as urgent where Db2 backs critical services or is reachable from untrusted networks.

Executive priority

Prioritize remediation for production Db2 systems supporting customer-facing, revenue, identity, or operational workloads. This CVE can cause outages without requiring privileges, so availability exposure matters more than data-loss concerns based on the supplied evidence.

Technical view

CVE-2023-30445 affects IBM Db2 for Linux, UNIX and Windows, including Db2 Connect Server, versions 10.5, 11.1, and 11.5. It is a CWE-20 input validation issue with CVSS 3.1 score 7.5: network exploitable, low complexity, no privileges, no user interaction, and high availability impact.

Likely exposure

Exposure is most likely in environments running IBM Db2 LUW or Db2 Connect Server 10.5, 11.1, or 11.5. Risk increases when Db2 services are reachable from broad internal networks, partners, or the internet. The sources do not identify unaffected fix levels.

Exploitation context

The CVE is not listed as CISA KEV in the supplied bundle, and no cited source states active exploitation. CVSS indicates remote unauthenticated reachability, but the described impact is denial of service through a crafted query on certain tables, not confidentiality or integrity compromise.

Researcher notes

The public bundle describes affected versions and impact but does not include root-cause internals, exact vulnerable table conditions, fixed builds, or exploit evidence. Validate exposure through asset inventory and vendor advisory comparison rather than attempting exploit reproduction.

Mitigation direction

  • Review IBM advisory 7010557 and apply IBM-supported fixes or configuration guidance.
  • Inventory Db2 LUW and Db2 Connect Server versions 10.5, 11.1, and 11.5.
  • Limit Db2 network access to trusted application hosts where feasible.
  • Review NetApp advisory if Db2 is embedded in or supports NetApp-managed environments.
  • Monitor Db2 availability and error patterns for unexplained query-triggered outages.

Validation and detection

  • Confirm installed Db2 major versions and fix pack levels against IBM advisory guidance.
  • Identify Db2 listeners reachable from untrusted or overly broad network segments.
  • Map business services dependent on affected Db2 instances.
  • Check change records for IBM-recommended updates or compensating controls.
  • Review incident logs for unexplained Db2 crashes or availability interruptions.
Prepared
Confidence
high
Sources
5

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 · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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
cve · low confidence lookup

CVE-2023-30445 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
0Timeline events
0ADP providers
4Source 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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-30445Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IBMDB2 for Linux, UNIX and Windows10.5, 11.1, 11.5unaffected
Weakness

CWE details

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

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.