CVE-2015-2912: OrientDB-Server vulnerable to Cross-Site Request Forgery

Summary

18/10/2018
Yes i
High
8.8

CVE-2015-2912: OrientDB-Server vulnerable to Cross-Site Request Forgery. Affects com.orientechnologies:orientdb-studio across 2 version ranges.

< 2.0.15 >= 2.1.0, < 2.1.1

Fixed in 2.0.15 or 2.1.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

OrientDB-Server is an open-source NoSQL database management system that provides support for graph, document, key-value, and object-oriented models. It includes a Studio component that offers a web-based interface for managing and querying databases. The vulnerability identified as CVE-2015-2912 affects OrientDB Server Community Edition versions before 2.0.15 and 2.1.x before 2.1.1. This vulnerability specifically targets the JSONP endpoint in the Studio component.

Vulnerability Detail

The JSONP endpoint 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. An attacker can exploit this vulnerability by crafting a malicious HTTP request to trick authenticated users into performing unintended actions on the affected OrientDB Server instance. This can lead to unauthorized access, data leakage, and potential compromise of the entire database.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.0.15 2.0.15
  • >= 2.1.0, < 2.1.1 2.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, users can disable the JSONP endpoint in the Studio component by modifying the server configuration. This can be achieved by setting the 'network.http.jsonp.enabled' property to 'false' in the 'orientdb-server-config.xml' file. However, this may impact the functionality of certain applications or integrations that rely on JSONP.

Conclusion

The vulnerability in OrientDB-Server allows for cross-site request forgery attacks, potentially leading to unauthorized access and data leakage. It is crucial to upgrade to the fixed versions mentioned in the 'how_to_fix' section to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for com.orientechnologies:orientdb-studio →

Share this vulnerability

FAQ

OrientDB-Server is an open-source NoSQL database management system that supports various data models.

The Studio component provides a web-based interface for managing and querying databases in OrientDB-Server.

Cross-Site Request Forgery (CSRF) is an attack that tricks authenticated users into performing unintended actions on a web application.

This vulnerability can lead to unauthorized access, data leakage, and potential compromise of the entire OrientDB Server database.

To mitigate this vulnerability, it is recommended to upgrade OrientDB Server Community Edition to the fixed versions mentioned in the 'how_to_fix' section.

Related vulnerabilities

Recent vulnerabilities recorded for com.orientechnologies:orientdb-studio.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.0.15 2.0.15
  • >= 2.1.0, < 2.1.1 2.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback