Oauth2Application · Owncloud
CVE-2023-49104
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpen redirect vulnerability in ownCloud oauth2 module before 0.6.1 allows attackers to bypass redirect URL validation when 'Allow Subdomains' is enabled, enabling malicious callback redirects to attacker-controlled TLDs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Oauth2Application
< 0.6.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify oauth2 module is installedRun `occ app:list` or check the ownCloud apps directory to confirm the oauth2 app is present and enabledAffected if oauth2 module is not installed or not applicable to the environment
-
Check oauth2 module versionRun `occ app:info oauth2` to retrieve the installed version number, or inspect the app's info.xml/version file in the apps directoryAffected if version is less than 0.6.1 (e.g., 0.6.0, 0.5.x, etc.)
-
Locate the Allow Subdomains settingAccess the ownCloud admin panel, navigate to OAuth2 settings (Settings > Authentication & authorization > OAuth2), or query the database table `oc_appconfig` for the key `allow-subdomains` in the `oauth2` app namespaceAffected if the Allow Subdomains setting is found and enabled (value is 'true' or '1')
-
Verify redirect URL validation is activeCheck the OAuth2 client configuration in the database table `oc_oauth2_clients` or via the admin UI to confirm redirect URIs are being validated against the configured allowed domainsAffected if redirect URL validation relies on the Allow Subdomains setting and no additional whitelist validation is in place
The environment is affected if the oauth2 module version is below 0.6.1 AND the Allow Subdomains setting is enabled, allowing attacker-controlled TLDs in redirect URIs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.6.1
Upgrade ownCloud oauth2 to version 0.6.1 or later, or disable 'Allow Subdomains' feature if not required.
0.6.1
- Upgrade the owncloud/oauth2 library to version 0.6.1 or later
- Verify the upgrade was successful by checking the installed version
- Test the OAuth2 redirect functionality to confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Oauth2
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-49104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-49104 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data