GHSA-W228-RFPX-FHM4
cg vulnerable to an Open Redirect Vulnerability on Referer Header
Overview
Description
Summary
A vulnerability has been discovered in the handling of the referrer header in the application, which could allow an attacker to conduct open redirects. The issue arises from improper validation of the referrer header in certain conditions. By manipulating the referrer header, an attacker could potentially redirect users to malicious websites, phishing pages, or other dangerous destinations.
PoC
If you change the referer header, you will be redirected to that domain without verifying.
https://github.com/Clinical-Genomics/cg/blob/master/cg/server/invoices/views.py#L173
Impact
An attacker exploiting this vulnerability could trick users into visiting malicious websites or disclose sensitive information by redirecting them to unintended destinations. This could lead to various attacks including phishing, malware distribution, or further exploitation of other vulnerabilities.
Source: OX vulnerability database
Severity
6.1 · MEDIUM
CVSS 3.1 base score, scored by GitHub.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Affected packages · 1
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| PyPI | cg | <60.2.12 | 60.2.12 |
Open a package to see all its vulnerabilities.
Operating systems
No Linux distribution reports this ID.
References
- github.com https://github.com/Clinical-Genomics/cg
- github.com https://github.com/Clinical-Genomics/cg/blob/master/cg/server/invoices/views.py#L173
- github.com https://github.com/Clinical-Genomics/cg/commit/96e6a968a5a3639cc40ad251ad65952e4f38dd25
- github.com https://github.com/Clinical-Genomics/cg/security/advisories/GHSA-w228-rfpx-fhm4
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.