What is the CVSS score of CVE-2021-27799?

CVE-2021-27799 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. EPSS exploitation probability: 2.4%.

Is there a public PoC exploit available for CVE-2021-27799?

Yes, a public proof-of-concept exploit is available for CVE-2021-27799. Prioritise patching immediately. EPSS: 2.4%.

Is there a patch available for CVE-2021-27799?

Yes, a patch is available for CVE-2021-27799. Update the affected software to the latest version immediately.

Barcode Generator CVE-2021-27799

HIGH

Out-of-bounds Write (CWE-787)

2021-02-26 cve@mitre.org

Buffer Overflow Memory Corruption Barcode Generator

7.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.5 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Lifecycle Timeline

CVE Published

Feb 26, 2021 - 22:15 nvd

HIGH 7.5

DescriptionNVD

AnalysisAI

ean_leading_zeroes in backend/upcean.c in Zint Barcode Generator 2.9.1 has a stack-based buffer overflow that is reachable from the C API through an application that includes the Zint Barcode. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Out-of-bounds Write (CWE-787), which allows attackers to write data beyond allocated buffer boundaries leading to code execution or crashes. ean_leading_zeroes in backend/upcean.c in Zint Barcode Generator 2.9.1 has a stack-based buffer overflow that is reachable from the C API through an application that includes the Zint Barcode Generator library code. Affected products include: Zint Barcode Generator.

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Validate write boundaries, use memory-safe languages, enable compiler protections (ASLR, stack canaries).