# CVE-2024-41801: OpenProject packaged installation has Open Redirect Vulnerability in Sign-In in default configuration > Attackers can redirect users to malicious sites via forged HOST headers in default OpenProject installations, facilitating phishing attacks. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 25 Jul 2024 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-g92v-vrq6-4fpw ## What is CVE-2024-41801? CVE-2024-41801 is a medium-severity vulnerability in opf openproject, published on 25 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description OpenProject is open source project management software. Prior to version 14.3.0, using a forged HOST header in the default configuration of packaged installations and using the "Login required" setting, an attacker could redirect to a remote host to initiate a phishing attack against an OpenProject user's account. This vulnerability affects default packaged installation of OpenProject without any additional configuration or modules on Apache (such as mod_security, manually setting a host name, having a fallthrough VirtualHost). It might also affect other installations that did not take care to fix the HOST/X-Forwarded-Host headers. Version 14.3.0 includes stronger protections for the hostname from within the application using the HostAuthorization middleware of Rails to reject any requests with a host name that does not match the configured one. Also, all generated links by the application are now ensured to use the built-in hostname. Users who aren't able to upgrade immediately may use mod_security for Apache2 or manually fix the Host and X-Forwarded-Host headers in their proxying application before reaching the application server of OpenProject. Alternatively, they can manually apply the patch to opt-in to host header protections in previous versions of OpenProject. Weakness: CWE-601 (URL Redirection to Untrusted Site) ## Which versions are affected by CVE-2024-41801? It affects 1 product. Products: Openproject Openproject. ## How do I fix CVE-2024-41801? No fix has been published for CVE-2024-41801 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-41801 being exploited? There is no known exploitation of CVE-2024-41801 in the wild and no public exploit code. ## Other vulnerabilities in opf openproject - [CVE-2026-34717](https://insights.sbomify.com/CVE-2026-34717/): OpenProject: SQL Injection in Cost Reporting =n Operator via parse_number_string (critical 9.9) - [CVE-2026-25763](https://insights.sbomify.com/CVE-2026-25763/): Command Injection on OpenProject repositories leads to Remote Code Execution (critical 9.4) - [CVE-2026-24685](https://insights.sbomify.com/CVE-2026-24685/): OpenProject has Argument Injection on Repository module that allows Arbitrary File Write (critical 9.4) - [CVE-2026-32698](https://insights.sbomify.com/CVE-2026-32698/): OpenProject has a SQL Injection via Custom Field Name that can be chained to Remote Code Execution (critical 9.1) - [CVE-2026-32703](https://insights.sbomify.com/CVE-2026-32703/): OpenProject's repository files are served with the MIME type allowing them to be used to bypass Content Security Policy (critical 9.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-41801 and fix it if it is affected. What it is: CVE-2024-41801 is a medium-severity vulnerability in opf openproject, published on 25 Jul 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2024-41801 in the wild and no public exploit code. Affected product: opf openproject. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-41801/ (Markdown: https://insights.sbomify.com/CVE-2024-41801/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41801 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41801 - OSV: https://osv.dev/vulnerability/CVE-2024-41801 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-41801/ Summaries are generated and may contain mistakes; the official description above is the record.