OwncloudApplication
CVE-2022-31649
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 · uneditedownCloud owncloud/core before 10.10.0 Improperly Removes Sensitive Information Before Storage or Transfer.
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 confidenceIn ownCloud core versions before 10.10.0, sensitive information is improperly handled before being stored or transferred, potentially allowing unauthorized access to sensitive data due to incomplete removal logic.
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.10.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Check ownCloud version via admin status pageLog into the ownCloud web interface as an administrator, navigate to the Settings > Administration > General page, and locate the version information displayed under 'ownCloud' or 'Version'.Affected if The displayed version number is less than 10.10.0 (for example, 10.9.0, 10.8.0, etc.)
-
Check ownCloud version via occ commandRun the command 'occ --version' or 'php occ --version' from the ownCloud installation directory (typically /var/www/owncloud or similar).Affected if The output shows a version lower than 10.10.0 (for example, 10.9.0, 10.8.0, etc.)
-
Check ownCloud version via API endpointSend a GET request to the ownCloud status API endpoint (e.g., curl https://your-owncloud-server.com/status.php) and parse the 'version' field in the JSON response.Affected if The version field in the response contains a number less than 10.10.0 (for example, '10.9.0.2').
-
Check version file directlyInspect the version.php file in the ownCloud installation directory (typically /var/www/owncloud/version.php or /var/www/html/owncloud/version.php) and read the version constant defined there.Affected if The defined version constant is less than '10.10.0'.
The environment is affected if the installed ownCloud core version is any version prior to 10.10.0 (such as 10.9.x, 10.8.x, or earlier).
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 · scoped10.10.0
Upgrade ownCloud core to version 10.10.0 or later to receive the patch for this improper sensitive data removal vulnerability.
ownCloud 10.10.0
- 1. Create a complete backup of the ownCloud data directory, database, and configuration files
- 2. Put ownCloud into maintenance mode via occ command: occ maintenance:mode --on
- 3. Download ownCloud server 10.10.0 from the official ownCloud downloads
- 4. Extract the new version files, overwriting the existing installation while preserving the config directory
- 5. Run the upgrade command: occ upgrade
- 6. Clear any application caches
- 7. Disable maintenance mode: occ maintenance:mode --off
- 8. Verify the installation by logging in and checking that ownCloud functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Owncloud
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31649 — 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-31649 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