Menu

Star on GitHub · 3.2k

CVE-2018-6764

7.8 · HIGH

util/virlog.c in libvirt does not properly determine the hostname on LXC container startup, which allows local guest OS users to bypass an intended container protection mechanism and execute arbitr…

Published Feb 23, 2018CWE-346EPSS 0.33%

Overview

CVE-2018-6764 is a high-severity vulnerability. It was published on February 23, 2018 and has a CVSS 3.0 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.0 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

util/virlog.c in libvirt does not properly determine the hostname on LXC container startup, which allows local guest OS users to bypass an intended container protection mechanism and execute arbitrary commands via a crafted NSS module.

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-6764?

CVE-2018-6764 is a high-severity vulnerability. It was published on February 23, 2018 and has a CVSS 3.0 base score of 7.8 (HIGH).

How severe is CVE-2018-6764?

This vulnerability has a CVSS 3.0 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

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

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-6764?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2018-6764 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 HIGH CVEs from 2018

View all