Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2021-3561: An Out of Bounds flaw was found fig2dev version 3.2.8a.

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.7% of all records.
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: fig2dev (Debian:12) 1:3.2.8-3; fig2dev (Debian:9) 1:3.2.6a-2+deb9u4; transfig (openSUSE:Leap 15.2) 3.2.8a-lp152.6.6.2.

Low priority for now. Upgrade to fig2dev (Debian:12) 1:3.2.8-3; fig2dev (Debian:9) 1:3.2.6a-2+deb9u4; transfig (openSUSE:Leap 15.2) 3.2.8a-lp152.6.6.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An Out of Bounds flaw was found fig2dev version 3.2.8a. A flawed bounds check in read_objects() could allow an attacker to provide a crafted malicious input causing the application to either crash or in some cases cause memory corruption. The highest threat from this vulnerability is to integrity as well as system availability.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
May 26, 2021
Updated
Jun 17, 2026
EPSS
1.1% · 67th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-3561

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
fig2dev projectfig2dev
fedoraprojectfedora
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux9.0
  • fedoraproject fedora33
  • fedoraproject fedora34
  • fig2dev project fig2dev3.2.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a fig2dev

    • fig2dev 3.2.8aaffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12fig2devbefore 1:3.2.8-31:3.2.8-3
Debian:9fig2devbefore 1:3.2.6a-2+deb9u41:3.2.6a-2+deb9u4
openSUSE:Leap 15.2transfigbefore 3.2.8a-lp152.6.6.23.2.8a-lp152.6.6.2
openSUSE:Leap 15.3transfigbefore 3.2.8a-4.12.23.2.8a-4.12.2
openSUSE:Leap 15.3transfigbefore 3.2.8a-bp153.3.3.23.2.8a-bp153.3.3.2
openSUSE:Tumbleweedtransfigbefore 3.2.8a-5.13.2.8a-5.1
SUSE:HPE Helion OpenStack 8transfigbefore 3.2.8a-2.17.13.2.8a-2.17.1
SUSE:Linux Enterprise Point of Sale 11 SP3transfigbefore 3.2.8a-1.160.13.13.2.8a-1.160.13.1
SUSE:Linux Enterprise Workstation Extension 15 SP2transfigbefore 3.2.8a-4.12.23.2.8a-4.12.2
SUSE:Package Hub 15 SP2transfigbefore 3.2.8a-bp152.3.3.23.2.8a-bp152.3.3.2
SUSE:Package Hub 15 SP3transfigbefore 3.2.8a-bp153.3.3.23.2.8a-bp153.3.3.2

Other highest-scoring records for the same primary product.

Published before and after this one in the same product

  • ← EarlierCVE-2019-19746Dec 11, 2019 · make_arrow in arrow.c in Xfig fig2dev 3.2.7b allows a segmentation fault and out-of-bounds write because of an integer overflow via a large
    22Monitor
  • Later →CVE-2020-21675Aug 10, 2021 · A stack-based buffer overflow in the genptk_text component in genptk.c of fig2dev 3.2.7b allows attackers to cause a denial of service (DOS)
    22Monitor
  • Later →CVE-2020-21676Aug 10, 2021 · A stack-based buffer overflow in the genpstrx_text() component in genpstricks.c of fig2dev 3.2.7b allows attackers to cause a denial of serv
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:fig2dev1:3.2.8-3 · Debian:12Package registry (OSV)
opensuse:transfig3.2.8a-bp153.3.3.2 · openSUSE:Leap 15.3Package registry (OSV)
opensuse:transfig3.2.8a-lp152.6.6.2 · openSUSE:Leap 15.2Package registry (OSV)
suse:transfig3.2.8a-1.160.13.1 · SUSE:Linux Enterprise Point of Sale 11 SP3Package registry (OSV)
suse:transfig3.2.8a-bp153.3.3.2 · SUSE:Package Hub 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records