CVE-2022-36151: tifig v0.2.2 was discovered to contain a segmentation violation via getType() at /common/bbox.cpp.

Routine

MEDIUM 5.5DOWNGRADE

CVE-2022-36151 is a medium-severity flaw (CVSS 5.5) affecting tifig. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

tifig v0.2.2 was discovered to contain a segmentation violation via getType() at /common/bbox.cpp.

Why this priority

Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 77%)
CISA exploited list	No
Weakness	CWE-476
Published	2022-08-16
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: monostream

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-08-16 21:15 UTCPublished CVE record published
2026-06-17 04:53 UTCUpdated Record last modified

monostream tifig DOWNGRADE

Affected: 0.2.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.2.2

1. Check installed version

apt-cache policy tifig || rpm -q tifig || tifig --version

2. No fixed release: DOWNGRADE to a release before 0.2.2 (Debian / Ubuntu)

apt-cache madison tifig sudo apt install tifig=<VERSION_BEFORE_0.2.2> sudo apt-mark hold tifig

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tifig sudo dnf downgrade tifig-<VERSION_BEFORE_0.2.2> sudo dnf versionlock add tifig

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-36151?

tifig: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-36151 being exploited?

CVE-2022-36151 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-36151 affect?

CVE-2022-36151 affects tifig. Severity is medium (CVSS 5.5). tifig v0.2.2 was discovered to contain a segmentation violation via getType() at /common/bbox.cpp.

How urgent is CVE-2022-36151?

Priority 30/100. Public exploit reference

Related CVEs

CVE-2022-36155 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a resource allocation issue via operator new(unsigned long) at asan_new
CVE-2022-36153 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a segmentation violation via std::vector<unsigned int, std::allocator<u
CVE-2022-36152 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a memory leak via operator new[](unsigned long) at /asan/asan_new_delet
CVE-2022-36150 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a heap-buffer overflow via __asan_memmove at /asan/asan_interceptors_me
CVE-2022-36149 MEDIUM 5.5 DOWNGRADE tifig v0.2.2 was discovered to contain a heap-use-after-free via temInfoEntry().

References

← Back to latest CVEs