# CVE-2021-3113: Information disclosure in n/a

> Remote attackers can discover active session cookies via an unprotected endpoint, potentially leading to admin account takeover.

- **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:** 17 Jan 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-64f9-rvmm-2r5q

## What is CVE-2021-3113?

CVE-2021-3113 is a high-severity vulnerability in n/a, published on 17 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netsia SEBA+ through 0.16.1 build 70-e669dcd7 allows remote attackers to discover session cookies via a direct /session/list/allActiveSession request. For example, the attacker can discover the admin's cookie if the admin account happens to be logged in when the allActiveSession request occurs, and can then use that cookie immediately for admin access,

Weakness: CWE-425 (Direct Request)

## Which versions are affected by CVE-2021-3113?

It affects 1 product.


Products: Netsia Seba\+.

## How do I fix CVE-2021-3113?

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

## Is CVE-2021-3113 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3113 and fix it if it is affected.

What it is: CVE-2021-3113 is a high-severity vulnerability in n/a, published on 17 Jan 2021. 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-2021-3113 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-2021-3113/ (Markdown: https://insights.sbomify.com/CVE-2021-3113/index.md)
```

## Sources

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

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