# CVE-2023-49104: Open redirect in n/a

> Attackers can bypass redirect validation to send OAuth callbacks to attacker-controlled domains when subdomain support is enabled.

- **Severity:** High 8.7 (`CVSS:3.1/AC:H/AV:N/A:N/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2023
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-phfx-x4q3-w99v

## What is CVE-2023-49104?

CVE-2023-49104 is a high-severity vulnerability in n/a, published on 21 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in ownCloud owncloud/oauth2 before 0.6.1, when Allow Subdomains is enabled. An attacker is able to pass in a crafted redirect-url that bypasses validation, and consequently allows an attacker to redirect callbacks to a Top Level Domain controlled by the attacker.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2023-49104?

It affects 1 product.


Products: Owncloud Oauth2.

## How do I fix CVE-2023-49104?

No fix has been published for CVE-2023-49104 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-49104 being exploited?

There is no known exploitation of CVE-2023-49104 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49104 and fix it if it is affected.

What it is: CVE-2023-49104 is a high-severity vulnerability in n/a, published on 21 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-49104 in the wild and no public exploit code.

Affected product: n/a. 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-2023-49104/ (Markdown: https://insights.sbomify.com/CVE-2023-49104/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-49104
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-49104
- OSV: https://osv.dev/vulnerability/CVE-2023-49104

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-49104/
Summaries are generated and may contain mistakes; the official description above is the record.