Menu

Star on GitHub · 3.2k

CVE-2018-1799

6.2 · MEDIUM

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 da…

Published Nov 9, 2018EPSS 0.43%

Overview

CVE-2018-1799 is a medium-severity vulnerability. It was published on November 9, 2018 and has a CVSS 3.0 base score of 6.2 (MEDIUM).

This vulnerability has a CVSS 3.0 base score of 6.2, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2018-1799?

CVE-2018-1799 is a medium-severity vulnerability. It was published on November 9, 2018 and has a CVSS 3.0 base score of 6.2 (MEDIUM).

How severe is CVE-2018-1799?

This vulnerability has a CVSS 3.0 base score of 6.2, rated MEDIUM. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2018-1799?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2018-1799?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2018-1799 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2018

View all