CVE-2024-30142: HCL BigFix Compliance is affected by a missing secure flag on a cookie

Routine

LOW 3.8DOWNGRADE

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

HCL BigFix Compliance is affected by a missing secure flag on a cookie. If a secure flag is not set, cookies may be stolen by an attacker using XSS, resulting in unauthorized access or session cookies could be transferred over an unencrypted channel.

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	3.8 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 99%)
CISA exploited list	No
Weakness	CWE-614
Published	2024-11-07
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-11-07 09:15 UTCPublished CVE record published
2026-06-17 07:26 UTCUpdated Record last modified

hcltech bigfix compliance DOWNGRADE

Affected: 2.0.11

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.11

1. Check installed version

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

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

apt-cache madison bigfix-compliance sudo apt install bigfix-compliance=<VERSION_BEFORE_2.0.11> sudo apt-mark hold bigfix-compliance

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

dnf --showduplicates list bigfix-compliance sudo dnf downgrade bigfix-compliance-<VERSION_BEFORE_2.0.11> sudo dnf versionlock add bigfix-compliance

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-30142?

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

Is CVE-2024-30142 being exploited?

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

CVE-2024-30142 affects bigfix compliance. Severity is low (CVSS 3.8). HCL BigFix Compliance is affected by a missing secure flag on a cookie. If a secure flag is not set, cookies may be stolen by an attacker using XSS, resulting in unauthorized access or session cookies could be transferred over an unencrypt

How urgent is CVE-2024-30142?

Priority 14/100. No elevated risk signals yet.

Related CVEs

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-2024-30125 MEDIUM 6.2 UPGRADE HCL BigFix Compliance server can respond with an HTTP status of 500, indicating a server-side error that may c
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