OwncloudApplication
CVE-2022-43679
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 · uneditedThe Docker image of ownCloud Server through 10.11 contains a misconfiguration that renders the trusted_domains config useless. This could be abused to spoof the URL in password-reset e-mail messages.
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 · moderate confidenceThe Docker image of ownCloud Server through version 10.11 contains a misconfiguration that bypasses the trusted_domains security control. This allows attackers to specify arbitrary hostnames, enabling spoofed URLs in password-reset email messages.
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
OwncloudApplication
<= 10.11.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm ownCloud is running in DockerRun 'docker ps' or inspect your container orchestration to verify ownCloud is deployed as a Docker containerAffected if ownCloud is NOT running as a Docker container, this specific CVE does not apply
-
Check installed ownCloud versionAccess the ownCloud admin panel and navigate to Settings > General > Version, or run 'docker exec <container> cat version.php' to view the version fileAffected if version is greater than 10.11.0 - the CVE only affects versions <= 10.11.0
-
Locate and read the config.php file in the Docker containerRun 'docker exec <container> cat /var/www/html/config/config.php' to access the configuration fileAffected if the config.php file cannot be accessed or does not exist in the expected Docker path
-
Inspect the trusted_domains setting in config.phpSearch the config.php output for the 'trusted_domains' array entry and examine its valuesAffected if trusted_domains is either missing entirely, contains a single wildcard '*', or contains no restrictive domain entries allowing arbitrary hostnames
You are affected if running ownCloud version <= 10.11.0 as a Docker container with misconfigured or overly permissive trusted_domains in config.php.
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 · scopedProperly configure the trusted_domains setting in ownCloud's config.php within the Docker container to restrict accepted domains and prevent hostname spoofing.
ownCloud Server 10.12.0 or later
- Upgrade ownCloud Server to version 10.12.0 or later to obtain a Docker image with the trusted_domains misconfiguration fixed
- If using Docker, pull the updated official ownCloud Docker image: docker pull owncloud/server:10.12.0 (or latest 10.x tag)
- Redeploy the ownCloud container with the updated image
- After upgrade, verify that the trusted_domains configuration in config/config.php is properly enforced by attempting to access the server from an untrusted domain - the request should be blocked
- Review and test password-reset email functionality to confirm URLs are now generated correctly based on trusted_domains
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Owncloud
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43679 — 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-2022-43679 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