# CVE-2024-42194: HCL BigFix Inventory is affected by an access control vulnerability

> An attacker with a read-only account can modify configuration parameters via crafted REST API calls due to insufficient permission checks.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Dec 2024
- **Updated:** 17 Dec 2024
- **Also known as:** GHSA-cr9c-4pg9-32j3

## What is CVE-2024-42194?

CVE-2024-42194 is a low-severity missing authorization vulnerability in HCL Software BigFix Inventory, published on 17 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An improper handling of insufficient permissions or privileges affects HCL BigFix Inventory.  An attacker having access via a read-only account can possibly change certain configuration parameters by crafting a specific REST API call.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

## Which versions are affected by CVE-2024-42194?


## How do I fix CVE-2024-42194?

No fix has been published for CVE-2024-42194 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42194 being exploited?

There is no known exploitation of CVE-2024-42194 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42194 and fix it if it is affected.

What it is: CVE-2024-42194 is a low-severity missing authorization vulnerability in HCL Software BigFix Inventory, published on 17 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42194 in the wild and no public exploit code.

Affected product: HCL Software BigFix Inventory. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-42194/ (Markdown: https://insights.sbomify.com/CVE-2024-42194/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-42194
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-42194
- OSV: https://osv.dev/vulnerability/CVE-2024-42194

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-42194/
Summaries are generated and may contain mistakes; the official description above is the record.