Skip to content
Fencer Vulns
high 7.1

CVE-2022-0497 json

A vulnerbiility was found in Openscad, where a .scad file with no trailing newline could cause an out-of-bounds read during parsing of anno…

published 2022-08-29 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-15634

cvss
7.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

A vulnerbiility was found in Openscad, where a .scad file with no trailing newline could cause an out-of-bounds read during parsing of annotations.

Patch / fix

  • openscad openscad 2022-01-09
  • openscad Debian 13, Debian 12 2021.01-4

debian advisories DEBIAN-CVE-2022-0497

  • openscad openSUSE Tumbleweed 2021.01-4.1

opensuse advisories openSUSE-SU-2024:11817-1

  • openscad Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 2021.01-r2

alpine advisories ALPINE-CVE-2022-0497

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-0497 updated cvss 7.1

openscad: Out-of-bounds memory access in comment parser

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/openscad/openscad/issues/4043 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H

Affected products

  • n/a openscad

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.