CVE-2015-2918
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 Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 does not properly restrict use of FRAME elements, which makes it easier for remote attackers to conduct clickjacking attacks via a crafted web site.
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 confidenceOrientDB Studio component fails to restrict FRAME element usage, allowing the application to be embedded in arbitrary iframes. Attackers can overlay invisible or disguised UI elements to trick users into performing unintended actions (clickjacking). This is a classic missing X-Frame-Options or Content-Security-Policy header issue.
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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Identify OrientDB versionRun 'java -jar orientdb-server.jar -version' or check the version file in the OrientDB installation directory, or query the server via REST API endpointAffected if The installed version is 2.0.14 or 2.1.0 specifically
-
Confirm OrientDB Studio is accessibleAccess the Studio web interface (typically at port 2480) via HTTP and verify the application loadsAffected if Studio is reachable and responds to HTTP requests on the configured port
-
Inspect X-Frame-Options headerSend an HTTP request to the Studio endpoint (e.g., GET /studio/) and examine the response headers for X-Frame-OptionsAffected if The X-Frame-Options header is missing, or absent with value DENY or SAMEORIGIN
-
Inspect Content-Security-Policy headerSend an HTTP request to the Studio endpoint and examine the response headers for Content-Security-Policy headerAffected if The CSP header is missing, or does not include a frame-ancestors directive that restricts framing
A user is affected if they are running OrientDB version 2.0.14 or 2.1.0 with Studio accessible, and neither X-Frame-Options nor Content-Security-Policy with frame-ancestors is configured to prevent clickjacking.
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 to version 2.0.15 or later (2.1.x to 2.1.1 or later), or configure the web server to send X-Frame-Options: DENY/SAMEORIGIN or Content-Security-Policy with frame-ancestors directive to prevent framing.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2918 — 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-2918 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