CVE-2020-36619: A vulnerability was found in multimon-ng

Q: How do I fix CVE-2020-36619?

multimon-ng: upgrade to 1.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-36619 being exploited?

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

Q: What does CVE-2020-36619 affect?

CVE-2020-36619 affects multimon-ng. Severity is medium (CVSS 5.5). 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 addr

Q: How urgent is CVE-2020-36619?

Priority 35/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

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

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.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.0% (top 38%)
CISA exploited list	No
Weakness	CWE-119, CWE-134
Published	2022-12-19
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: multimon-ng project

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

Am I affected?

Timeline

2022-12-19 14:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

multimon-ng project multimon-ng UPGRADE

Affected: < 1.2.0

Fixed in: 1.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy multimon-ng || rpm -q multimon-ng || multimon-ng --version

2. UPGRADE to 1.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade multimon-ng

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade multimon-ng

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2020-36619?

multimon-ng: upgrade to 1.2.0. Exact commands for each OS are on this page.

Is CVE-2020-36619 being exploited?

CVE-2020-36619 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-2020-36619 affect?

CVE-2020-36619 affects multimon-ng. Severity is medium (CVSS 5.5). 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 addr

How urgent is CVE-2020-36619?

Priority 35/100. No elevated risk signals yet.

References

← Back to latest CVEs