Menu

Star on GitHub · 3.2k

CVE-2017-2627

8.2 · HIGH

A flaw was found in openstack-tripleo-common as shipped with Red Hat Openstack Enterprise 10 and 11.

Published Aug 22, 2018CWE-22EPSS 0.66%

Overview

CVE-2017-2627 is a high-severity vulnerability. It was published on August 22, 2018 and has a CVSS 3.0 base score of 8.2 (HIGH).

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

Technical description

A flaw was found in openstack-tripleo-common as shipped with Red Hat Openstack Enterprise 10 and 11. The sudoers file as installed with OSP's openstack-tripleo-common package is much too permissive. It contains several lines for the mistral user that have wildcards that allow directory traversal with '..' and it grants full passwordless root access to the validations user.

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-2017-2627?

CVE-2017-2627 is a high-severity vulnerability. It was published on August 22, 2018 and has a CVSS 3.0 base score of 8.2 (HIGH).

How severe is CVE-2017-2627?

This vulnerability has a CVSS 3.0 base score of 8.2, 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-2017-2627?

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-2017-2627?

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

View all