# CVE-2015-2913: OrientDB Server Community Edition uses insufficiently random values to generate session IDs

> Attackers can predict session IDs due to weak random number generation, potentially leading to account takeover in OrientDB Server.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-v6wr-fch2-vm5w

## What is CVE-2015-2913?

CVE-2015-2913 is a medium-severity vulnerability in n/a, published on 31 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

server/network/protocol/http/OHttpSessionManager.java in the Studio component in OrientDB Server Community Edition before 2.0.15 and 2.1.x before 2.1.1 improperly relies on the java.util.Random class for generation of random Session ID values, which makes it easier for remote attackers to predict a value by determining the internal state of the PRNG in this class.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-2913?

4 open source packages ship an affected version, including com.orientechnologies:orientdb-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.orientechnologies:orientdb-server` | Maven | All versions | 2.0.15 |
| `com.orientechnologies:orientdb-server` | Maven | All versions | 2.0.15 |
| `com.orientechnologies:orientdb-server` | Maven | From 2.1.0 | 2.1.1 |
| `com.orientechnologies:orientdb-server` | Maven | From 2.1.0 | 2.1.1 |

Products: Orientdb Orientdb.

## How do I fix CVE-2015-2913?

Upgrade com.orientechnologies:orientdb-server to a fixed version for your release line: 2.0.15 or 2.1.1.

## Is CVE-2015-2913 being exploited?

There is no known exploitation of CVE-2015-2913 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2017-11467](https://insights.sbomify.com/CVE-2017-11467/): OrientDB vulnerable to Improper Privilage Management leading to arbitrary command injection (critical 9.8)
- [CVE-2015-2912](https://insights.sbomify.com/CVE-2015-2912/): OrientDB-Server vulnerable to Cross-Site Request Forgery (high 8.8)
- [CVE-2015-2918](https://insights.sbomify.com/CVE-2015-2918/): OrientDB Studio web management interface is vulnerable to clickjacking attacks (medium 6.1)
- [CVE-2019-25447](https://insights.sbomify.com/CVE-2019-25447/): OrientDB 3.0.17 Cross-Site Request Forgery (medium 5.3)
- [CVE-2019-25448](https://insights.sbomify.com/CVE-2019-25448/): OrientDB 3.0.17 Stored Cross-Site Scripting via User Creation (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2913 and fix it if it is affected.

What it is: CVE-2015-2913 is a medium-severity vulnerability in n/a, published on 31 Dec 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2913 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.orientechnologies:orientdb-server (Maven): affected all versions; fixed in 2.0.15
- com.orientechnologies:orientdb-server (Maven): affected all versions; fixed in 2.0.15
- com.orientechnologies:orientdb-server (Maven): affected from 2.1.0; fixed in 2.1.1
- com.orientechnologies:orientdb-server (Maven): affected from 2.1.0; fixed in 2.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2913/ (Markdown: https://insights.sbomify.com/CVE-2015-2913/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2913
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2913
- OSV: https://osv.dev/vulnerability/CVE-2015-2913

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2913/
Summaries are generated and may contain mistakes; the official description above is the record.