OwncloudApplication
CVE-2012-2397
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 · uneditedCross-site request forgery (CSRF) vulnerability in ownCloud before 3.0.3 allows remote attackers to hijack the authentication of arbitrary users for requests that insert cross-site scripting (XSS) sequences via vectors involving contacts.
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 confidenceA CSRF vulnerability in ownCloud versions before 3.0.3 allows remote attackers to craft malicious requests that, when triggered by an authenticated user, can inject XSS sequences through the contacts functionality. The attack hijacks the user's authentication to perform unauthorized actions that embed malicious scripts.
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
<= 3.0.2
Owncloud ServerApplication
= 3.0.0= 3.0.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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Determine installed ownCloud versionAccess the ownCloud web interface and look at the footer for the version number, or inspect the config/config.php file for a version entry.Affected if The version is 3.0.2 or lower, or specifically 3.0.0 or 3.0.1 for the Server variant.
-
Verify if contacts application is enabledCheck if the contacts app is present and activated in ownCloud. This can be done by inspecting the apps/contacts directory or checking the app configuration in the ownCloud admin panel.Affected if The contacts application is enabled and users can access it.
-
Confirm active user sessions existCheck for active authenticated sessions on the ownCloud server. This vulnerability requires an authenticated user to trigger the malicious request.Affected if Users have active authenticated sessions on the ownCloud instance.
-
Identify web-facing accessibilityDetermine if the ownCloud web interface is accessible from the network or internet. The CSRF attack requires the victim to access a malicious page while logged into ownCloud.Affected if The ownCloud web interface is network-accessible to potential attackers.
A user is affected if their ownCloud version is 3.0.2 or lower (or 3.0.0/3.0.1 for Server) AND the contacts application is enabled AND users have active authenticated sessions that could be exploited via CSRF.
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.
From vendor dataUpgrade ownCloud to version 3.0.3 or later, which includes proper CSRF protection mechanisms. As an interim measure, ensure users are educated not to click untrusted links while logged into ownCloud.
Fix this in Owncloud
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-2012-2397 — 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-2012-2397 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