CVE-2024-29500: An issue in the kiosk mode of Secure Lockdown Multi Application Edition v2.00.219 allows attackers to execute

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-29500 is a critical-severity flaw (CVSS 9.8) affecting secure lockdown. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue in the kiosk mode of Secure Lockdown Multi Application Edition v2.00.219 allows attackers to execute arbitrary code via running a ClickOnce application instance.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-94
Published	2024-04-10
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: inteset

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

Am I affected?

Timeline

2024-04-10 20:15 UTCPublished CVE record published
2026-06-17 07:22 UTCUpdated Record last modified

inteset secure lockdown DOWNGRADE

Affected: 2.00.219

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.00.219

1. Check installed version

apt-cache policy secure-lockdown || rpm -q secure-lockdown || secure-lockdown --version

2. No fixed release: DOWNGRADE to a release before 2.00.219 (Debian / Ubuntu)

apt-cache madison secure-lockdown sudo apt install secure-lockdown=<VERSION_BEFORE_2.00.219> sudo apt-mark hold secure-lockdown

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list secure-lockdown sudo dnf downgrade secure-lockdown-<VERSION_BEFORE_2.00.219> sudo dnf versionlock add secure-lockdown

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2024-29500?

secure lockdown: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-29500 being exploited?

CVE-2024-29500 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-2024-29500 affect?

CVE-2024-29500 affects secure lockdown. Severity is critical (CVSS 9.8). An issue in the kiosk mode of Secure Lockdown Multi Application Edition v2.00.219 allows attackers to execute arbitrary code via running a ClickOnce application instance.

How urgent is CVE-2024-29500?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-29502 MEDIUM 6.5 DOWNGRADE An issue in Secure Lockdown Multi Application Edition v2.00.219 allows attackers to read arbitrary files via u

References

← Back to latest CVEs