# CVE-2024-0242: Unauthorized access to settings in Qolsys IQ Panel 4 and IQ4 Hub

> Attackers can gain unauthorized access to settings on Qolsys IQ Panel 4 and IQ4 Hub devices, potentially exposing sensitive configuration data.

- **Severity:** High 7.3 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-mc3m-gj6r-2fhp

## What is CVE-2024-0242?

CVE-2024-0242 is a high-severity vulnerability in Qolsys, Inc. IQ Panel 4, published on 8 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Under certain circumstances IQ Panel4 and IQ4 Hub panel software prior to version 4.4.2 could allow unauthorized access to settings.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 2 products.


Products: Johnsoncontrols Qolsys Iq4 Hub Firmware, Johnsoncontrols Qolsys Iq Panel 4 Firmware.

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

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

## Is CVE-2024-0242 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0242 is a high-severity vulnerability in Qolsys, Inc. IQ Panel 4, published on 8 Feb 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0242 in the wild and no public exploit code.

Affected product: Qolsys, Inc. IQ Panel 4. 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-0242/ (Markdown: https://insights.sbomify.com/CVE-2024-0242/index.md)
```

## Sources

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

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