How severe is CVE-2018-1799?

CVE-2018-1799 has a CVSS 3.x base score of 6.2, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.

Is CVE-2018-1799 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-1799?

CVE-2018-1799 primarily affects Ibm Db2. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2018-1799?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2018-1799 published?

CVE-2018-1799 was published on 2018-11-09 and last updated on 2026-06-17.

CVE-2018-1799

CVE-2018-1799 is a medium-severity vulnerability in Ibm Db2 with a CVSS 3.x base score of 6.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 3.x base score 6.2)
CVSS v2: 3.6
EPSS exploit prediction: 0% (34th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Ibm Db2
Published: 2018-11-09
Last modified: 2026-06-17

Description

IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, and 11.1 could allow a local unprivileged user to overwrite files on the system which could cause damage to the database. IBM X-Force ID: 149429.

Frequently asked questions

What is CVE-2018-1799?: IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, and 11.1 could allow a local unprivileged user to overwrite files on the system which could cause damage to the database. IBM X-Force ID: 149429.
How severe is CVE-2018-1799?: CVE-2018-1799 has a CVSS 3.x base score of 6.2, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
Is CVE-2018-1799 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (34th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-1799?: CVE-2018-1799 primarily affects Ibm Db2. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2018-1799?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2018-1799 published?: CVE-2018-1799 was published on 2018-11-09 and last updated on 2026-06-17.

References

Affected products (4)

cpe:2.3:a:ibm:db2:9.7:*:*:*:*:*:*:*
cpe:2.3:a:ibm:db2:10.1:*:*:*:*:*:*:*
cpe:2.3:a:ibm:db2:10.5:*:*:*:*:*:*:*
cpe:2.3:a:ibm:db2:11.1:*:*:*:*:*:*:*

More vulnerabilities in Ibm Db2

CVE-2012-1797 — Critical (CVSS 10.0): IBM DB2 9.5 uses world-writable permissions for nodes.reg, which has unspecified impact and attack vectors.
CVE-2010-3731 — Critical (CVSS 10.0): Stack-based buffer overflow in the validateUser implementation in the com.ibm.db2.das.core.DasSysCmd function in…
CVE-2010-3193 — Critical (CVSS 10.0): Unspecified vulnerability in the DB2STST program in IBM DB2 9.1 before FP9, 9.5 before FP6, and 9.7 before FP2 has…
CVE-2009-4335 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in bundled stored procedures in the Spatial Extender component in IBM DB2 9.5…
CVE-2009-3473 — Critical (CVSS 10.0): IBM DB2 9.1 before FP8 does not require the SETSESSIONUSER privilege for the SET SESSION AUTHORIZATION statement, which…
CVE-2008-6821 — Critical (CVSS 10.0): Buffer overflow in the DAS server in IBM DB2 8 before FP17, 9.1 before FP5, and 9.5 before FP2 might allow attackers to…

All CVEs affecting Ibm Db2 →