CVE-2015-2912
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 JSONP endpoint in the Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 does not properly restrict callback values, which allows remote attackers to conduct cross-site request forgery (CSRF) attacks, and obtain sensitive information, via a crafted HTTP request.
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 confidenceThe OrientDB Studio component contains a JSONP endpoint that fails to properly validate the callback parameter, allowing attackers to inject arbitrary JavaScript function names. This enables CSRF attacks by tricking authenticated users' browsers into making requests that return malicious JSONP responses, potentially exposing sensitive data from the OrientDB server.
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<= 2.0.14= 2.1.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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify OrientDB Studio component exposureCheck if the OrientDB Studio web interface is accessible. Look for HTTP endpoints under /studio/ or /webconsole/ paths. Review server configuration files (orientdb-server-config.xml) for studio/webconsole connector settings and network bindings.Affected if Studio component is enabled and exposed on a network-accessible interface (not localhost only)
-
Determine installed OrientDB versionCheck the OrientDB version by inspecting the server startup logs, the lib/ folder jar file names, or by querying the OSystemMetadata table via console/OSQL. Compare the version number against the affected ranges: <= 2.0.14 or exactly 2.1.0Affected if Installed version is 2.0.14 or earlier, or exactly 2.1.0
-
Verify JSONP endpoint accessibilityAccess the OrientDB Studio REST API endpoint that supports JSONP callbacks. Typical endpoints include /studio/command or /studio/query. Add a callback parameter with a test value like 'testfunc' to observe if the response wraps the JSON in the provided function name.Affected if The endpoint returns responses wrapped in a JavaScript function call using the supplied callback parameter value without sanitization
-
Test for callback parameter injectionSend a crafted request to a JSONP-capable endpoint with a callback value containing arbitrary characters such as 'alert(1)//' or 'malicious;'. Inspect whether the server reflects these characters unfiltered in the response Content-Type header indicating application/javascript.Affected if Arbitrary callback values are reflected in the response without validation or encoding, allowing arbitrary JavaScript function injection
Your environment is affected if OrientDB Studio is exposed and the installed version is 2.0.14 or earlier, or exactly 2.1.0, and the JSONP endpoint accepts arbitrary callback parameter values without validation.
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 OrientDB Server to version 2.0.15 or later (for 2.0.x branch) or 2.1.1 or later (for 2.1.x branch) to obtain the fixed Studio component with proper callback value restrictions.
- 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-2015-2912 — 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-2015-2912 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