# CVE-2021-36981: Deserialization in n/a

> Remote authenticated attackers can execute arbitrary code via insecure Java deserialization in the verinice server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Aug 2021
- **Updated:** 4 Aug 2024

## What is CVE-2021-36981?

CVE-2021-36981 is a high-severity unsafe deserialization vulnerability in n/a, published on 31 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the server in SerNet verinice before 1.22.2, insecure Java deserialization allows remote authenticated attackers to execute arbitrary code.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Sernet Verinice.

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

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

## Is CVE-2021-36981 being exploited?

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

Public exploit code:

- https://github.com/0xBrAinsTorM/CVE-2021-36981 (github_poc): https://github.com/0xBrAinsTorM/CVE-2021-36981

## Fix prompt for AI coding agents

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

What it is: CVE-2021-36981 is a high-severity unsafe deserialization vulnerability in n/a, published on 31 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36981 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-36981/ (Markdown: https://insights.sbomify.com/CVE-2021-36981/index.md)
```

## Sources

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

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