CVE-2020-36619

CVE-2020-36619 is a medium-severity vulnerability in Multimon-ng Project Multimon-ng with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-134.

Key facts

Description

A vulnerability was found in multimon-ng. It has been rated as critical. This issue affects the function add_ch of the file demod_flex.c. The manipulation of the argument ch leads to format string. Upgrading to version 1.2.0 is able to address this issue. The name of the patch is e5a51c508ef952e81a6da25b43034dd1ed023c07. It is recommended to upgrade the affected component. The identifier VDB-216269 was assigned to this vulnerability.

Frequently asked questions

What is CVE-2020-36619?
A vulnerability was found in multimon-ng. It has been rated as critical. This issue affects the function add_ch of the file demod_flex.c. The manipulation of the argument ch leads to format string. Upgrading to version 1.2.0 is able to address this issue. The name of the patch is e5a51c508ef952e81a6da25b43034dd1ed023c07. It is recommended to upgrade the affected component. The identifier VDB-216269 was assigned to this vulnerability.
How severe is CVE-2020-36619?
CVE-2020-36619 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over an adjacent network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2020-36619 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (55th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-36619?
CVE-2020-36619 affects Multimon-ng Project Multimon-ng. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-36619?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-36619 published?
CVE-2020-36619 was published on 2022-12-19 and last updated on 2026-06-17.

References

Affected products (1)

Other CWE-134 vulnerabilities

Browse all CWE-134 vulnerabilities →