GitLab Community Edition/Enterprise Edition up to 17.4.5/17.5.3/17.6.1 NEL Header redirect

Summaryinfo

A vulnerability identified as problematic has been detected in GitLab Community Edition and Enterprise Edition up to 17.4.5/17.5.3/17.6.1. Affected by this issue is some unknown functionality of the component NEL Header Handler. This manipulation causes redirect. This vulnerability is tracked as CVE-2024-11274. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in GitLab Community Edition and Enterprise Edition up to 17.4.5/17.5.3/17.6.1 and classified as problematic. Affected by this vulnerability is some unknown functionality of the component NEL Header Handler. The manipulation with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect integrity. The summary by CVE is:

An issue was discovered in GitLab CE/EE affecting all versions starting from 16.1 prior to 17.4.6, starting from 17.5 prior to 17.5.4, and starting from 17.6 prior to 17.6.2, injection of NEL headers in k8s proxy response could lead to session data exfiltration.

The weakness was disclosed by joaxcar as 504707. The advisory is shared at gitlab.com. This vulnerability is known as CVE-2024-11274 since 11/15/2024. The exploitation appears to be easy. The attack can be launched remotely. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1204.001 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 212681 (GitLab 16.1 < 17.4.6 / 17.5 < 17.5.4 / 17.6 < 17.6.2 (CVE-2024-11274)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 17.4.6, 17.5.4 or 17.6.2 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (212681). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Bug Tracking Software

Vendor

• GitLab

Name

• Community Edition
• Enterprise Edition

Version

• 17.4.0
• 17.4.1
• 17.4.2
• 17.4.3
• 17.4.4
• 17.4.5
• 17.5.0
• 17.5.1
• 17.5.2
• 17.5.3
• 17.6.0
• 17.6.1

License

• open-source

Website

• Vendor: https://gitlab.com/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion