CVE-2019-7323: GUP (generic update process) in LightySoft LogMX before 7.4.0 does not properly verify the authenticity of upd

Q: How do I fix CVE-2019-7323?

logmx: upgrade to 7.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2019-7323 being exploited?

CVE-2019-7323 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-2019-7323 affect?

CVE-2019-7323 affects logmx. Severity is high (CVSS 7.5). GUP (generic update process) in LightySoft LogMX before 7.4.0 does not properly verify the authenticity of updates, which allows man-in-the-middle attackers to execute arbitrary code via a Trojan horse update. The update process relies on c

Q: How urgent is CVE-2019-7323?

Priority 48/100. High severity; Public exploit reference

This month

HIGH 7.5UPGRADE

CVE-2019-7323 is a high-severity flaw (CVSS 7.5) affecting logmx. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

GUP (generic update process) in LightySoft LogMX before 7.4.0 does not properly verify the authenticity of updates, which allows man-in-the-middle attackers to execute arbitrary code via a Trojan horse update. The update process relies on cleartext HTTP. The attacker could replace the LogMXUpdater.class file.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.1% (top 35%)
CISA exploited list	No
Weakness	CWE-345
Published	2019-02-04
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: logmx

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

Am I affected?

Timeline

2019-02-04 16:29 UTCPublished CVE record published
2026-06-17 02:40 UTCUpdated Record last modified

logmx logmx UPGRADE

Affected: < 7.4.0

Fixed in: 7.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to 7.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade logmx

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade logmx

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-2019-7323?

logmx: upgrade to 7.4.0. Exact commands for each OS are on this page.

Is CVE-2019-7323 being exploited?

CVE-2019-7323 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-2019-7323 affect?

CVE-2019-7323 affects logmx. Severity is high (CVSS 7.5). GUP (generic update process) in LightySoft LogMX before 7.4.0 does not properly verify the authenticity of updates, which allows man-in-the-middle attackers to execute arbitrary code via a Trojan horse update. The update process relies on c

How urgent is CVE-2019-7323?

Priority 48/100. High severity; Public exploit reference

References

← Back to latest CVEs