How severe is CVE-2021-45703?

No CVSS score has been assigned to CVE-2021-45703 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2021-45703?

CVE-2021-45703 affects the following packages: tectonic_xdv (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2021-45703?

Update tectonic_xdv to 0.1.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-45703 is resolved across your whole dependency graph.

How do I detect CVE-2021-45703 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tectonic_xdv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-45703 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2021-45703 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-45703 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-45703?

CVE-2021-45703 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 67th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-45703?

CVE-2021-45703 is classified as CWE-908 (CWE-908). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-45703 published, and has it been updated?

CVE-2021-45703 was published on June 17, 2022 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

🦀 crates.io

Not in CISA KEV

CVE-2021-45703 — tectonic_xdv

Fix: tectonic-typesetting/tectonic@cdff034

CVE-2021-45703 is a CWE-908 vulnerability in tectonic_xdv. A fix is available for tectonic_xdv — see the affected versions and patch details below.

Duplicate Advisory: `Read` on uninitialized buffer may cause UB ('tectonic_xdv' crate)

Also known asGHSA-qwvx-c8j7-5g75RUSTSEC-2021-0112

Published

Jun 17, 2022

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🦀tectonic_xdv

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-qwvx-c8j7-5g75. This link is maintained to preserve external references.

Original Description

Affected versions of this crate passes an uninitialized buffer to a user-provided Read implementation.

Arbitrary Read implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior.

The problem was fixed in commit cdff034 by zero-initializing the buffer before passing it to a user-provided Read implementation.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tectonic_xdv`	all versions	0.1.12`cargo update -p tectonic_xdv --precise 0.1.12`

Affected Products

1 product · 1 configurations

Application

tectonic xdvtectonic_xdv_project

< 0.1.12

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tectonic_xdv, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tectonic_xdv to 0.1.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-45703 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-qwvx-c8j7-5g75. This link is maintained to preserve external references. ## Original Description Affected versions of this crate passes an uninitialized buffer to a user-provided `Read` implementation. Arbitrary `Read` implementations can read from the uninitialized buffer (memory exposure) and also can return incorrect number of bytes written to the buffer. Reading from uninitialized memory produces undefined values that can quickly invoke undefined behavior. The problem was fixed in commit `cdff034` b

O3 Security · Impact-Aware SCA

Is CVE-2021-45703 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works