CVE-2024-30125: HCL BigFix Compliance server can respond with an HTTP status of 500, indicating a server-side error that may c

Q: How do I fix CVE-2024-30125?

bigfix compliance: upgrade to 2.0.11. Exact commands for each OS are on this page.

Q: Is CVE-2024-30125 being exploited?

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

CVE-2024-30125 affects bigfix compliance. Severity is medium (CVSS 6.2). HCL BigFix Compliance server can respond with an HTTP status of 500, indicating a server-side error that may cause the server process to die.

Q: How urgent is CVE-2024-30125?

Priority 22/100. No elevated risk signals yet.

Routine

MEDIUM 6.2UPGRADE

CVE-2024-30125 is a medium-severity flaw (CVSS 6.2) affecting bigfix compliance. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

HCL BigFix Compliance server can respond with an HTTP status of 500, indicating a server-side error that may cause the server process to die.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.2 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-918
Published	2024-07-18
Last modified	2026-06-17

Publisher (CNA): HCL Software · Vendor: hcltech

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

Am I affected?

Timeline

2024-07-18 18:15 UTCPublished CVE record published
2026-06-17 07:26 UTCUpdated Record last modified

hcltech bigfix compliance UPGRADE

Affected: < 2.0.11

Fixed in: 2.0.11

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bigfix-compliance || rpm -q bigfix-compliance || bigfix-compliance --version

2. UPGRADE to 2.0.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bigfix-compliance

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bigfix-compliance

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

bigfix compliance: upgrade to 2.0.11. Exact commands for each OS are on this page.

Is CVE-2024-30125 being exploited?

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

CVE-2024-30125 affects bigfix compliance. Severity is medium (CVSS 6.2). HCL BigFix Compliance server can respond with an HTTP status of 500, indicating a server-side error that may cause the server process to die.

How urgent is CVE-2024-30125?

Priority 22/100. No elevated risk signals yet.

Related CVEs

CVE-2024-30142 LOW 3.8 DOWNGRADE HCL BigFix Compliance is affected by a missing secure flag on a cookie
CVE-2024-30141 MEDIUM 4.7 DOWNGRADE HCL BigFix Compliance is vulnerable to the generation of error messages containing sensitive information
CVE-2024-30140 MEDIUM 5.4 DOWNGRADE HCL BigFix Compliance is affected by unvalidated redirects and forwards
CVE-2024-30126 MEDIUM 4.7 UPGRADE HCL BigFix Compliance is affected by a missing X-Frame-Options HTTP header which can allow an attacker to crea
CVE-2023-37525 MEDIUM 5.3 DOWNGRADE A sensitive information disclosure in HCL BigFix Compliance allows a remote attacker to access files under the

References

← Back to latest CVEs