Menu

Star on GitHub · 3.2k

CVE-2017-9268

4.4 · MEDIUM

In the open build service before 201707022 the wipetrigger and rebuild actions checked the wrong project for permissions, allowing authenticated users to cause operations on projects where they did…

Published Mar 1, 2018CWE-285EPSS 0.60%

Overview

CVE-2017-9268 is a medium-severity vulnerability. It was published on March 1, 2018 and has a CVSS 3.0 base score of 4.4 (MEDIUM).

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

Technical description

In the open build service before 201707022 the wipetrigger and rebuild actions checked the wrong project for permissions, allowing authenticated users to cause operations on projects where they did not have permissions leading to denial of service (resource consumption).

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

CVE-2017-9268 is a medium-severity vulnerability. It was published on March 1, 2018 and has a CVSS 3.0 base score of 4.4 (MEDIUM).

How severe is CVE-2017-9268?

This vulnerability has a CVSS 3.0 base score of 4.4, rated MEDIUM. 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-9268?

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

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

View all