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

> Attacker can achieve pre-auth remote code execution via unsafe deserialization in PrinterLogic Web Stack.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-56m9-5m6m-wm57

## What is CVE-2021-42631?

CVE-2021-42631 is a high-severity unsafe deserialization vulnerability in Printerlogic Virtual Appliance, published on 31 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PrinterLogic Web Stack versions 19.1.1.13 SP9 and below deserializes attacker controlled leading to pre-auth remote code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 2 products.


Products: Printerlogic Virtual Appliance, Printerlogic Web Stack.

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

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

## Is CVE-2021-42631 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-42631 is a high-severity unsafe deserialization vulnerability in Printerlogic Virtual Appliance, published on 31 Jan 2022. 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-42631 in the wild and no public exploit code.

Affected product: Printerlogic Virtual Appliance. 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-42631/ (Markdown: https://insights.sbomify.com/CVE-2021-42631/index.md)
```

## Sources

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

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