# CVE-2016-20007: Information disclosure in n/a

> Attackers can guess session names in the Drupal REST/JSON module, potentially leading to session hijacking and unauthorized access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** No
- **Published:** 31 Dec 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7rwq-q3mj-f9qw

## What is CVE-2016-20007?

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

### Official description

The REST/JSON project 7.x-1.x for Drupal allows session name guessing, aka SA-CONTRIB-2016-033. NOTE: This project is not covered by Drupal's security advisory policy.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2016-20007?

It affects 1 product.


Products: Rest\/Json Project Rest\/Json.

## How do I fix CVE-2016-20007?

No fix has been published for CVE-2016-20007 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-20007 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-20001](https://insights.sbomify.com/CVE-2016-20001/): Missing authorization in n/a (critical 9.8)
- [CVE-2016-20002](https://insights.sbomify.com/CVE-2016-20002/): Missing authorization in n/a (critical 9.8)
- [CVE-2016-20004](https://insights.sbomify.com/CVE-2016-20004/): Missing authorization in n/a (critical 9.8)
- [CVE-2016-20005](https://insights.sbomify.com/CVE-2016-20005/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-20003](https://insights.sbomify.com/CVE-2016-20003/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20007 and fix it if it is affected.

What it is: CVE-2016-20007 is a high-severity vulnerability in n/a, published on 31 Dec 2020. 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-2016-20007 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2016-20007/ (Markdown: https://insights.sbomify.com/CVE-2016-20007/index.md)
```

## Sources

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

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