CVE-2015-2913: Vulnerability in com.orientechnologies:orientdb-studio

Summary

18/10/2018
Yes i
Moderate
5.9

CVE-2015-2913: OrientDB Server Community Edition uses insufficiently random values to generate session IDs. Affects com.orientechnologies:orientdb-server 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

com.orientechnologies:orientdb-studio is a component of OrientDB Server Community Edition. It provides a Studio interface for managing and interacting with the OrientDB database. The vulnerability in this package affects versions before 2.0.15 and 2.1.x before 2.1.1. The vulnerability is related to the generation of random Session ID values in the Studio component, which relies on the java.util.Random class. This reliance on a predictable PRNG (Pseudo-Random Number Generator) makes it easier for remote attackers to predict the Session ID value by determining the internal state of the PRNG.

Vulnerability Detail

The vulnerability in com.orientechnologies:orientdb-studio allows remote attackers to predict Session ID values, which can have various ramifications. By predicting the Session ID, an attacker can potentially hijack user sessions, gain unauthorized access to sensitive information, or perform other malicious activities. The vulnerability is considered moderate in severity with a CVSS score of 5.9.

How To Fix

Latest published version: 3.2.57 as of 22 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

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

There is no specific workaround mentioned for this vulnerability. The recommended solution is to upgrade to the fixed versions as mentioned in the 'how_to_fix' section.

Conclusion

The vulnerability in com.orientechnologies:orientdb-studio allows remote attackers to predict Session ID values, potentially leading to unauthorized access and other malicious activities. It is recommended to upgrade to the fixed versions to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

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

Share this vulnerability

FAQ

The vulnerability allows remote attackers to predict Session ID values, potentially leading to session hijacking, unauthorized access, and other malicious activities.

Versions before 2.0.15 and 2.1.x before 2.1.1 of com.orientechnologies:orientdb-studio are affected.

No specific workaround is mentioned. Upgrading to the fixed versions is recommended.

The vulnerability is considered moderate in severity with a CVSS score of 5.9.

You can find more information about this vulnerability in the provided source link.

How To Fix

Latest published version: 3.2.57 as of 22 Oct 2026

Upgrading to it may include breaking changes; the versions below are the minimum fixed release for this vulnerability.

If you can't move to the latest

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