# CVE-2015-6032: Hardcoded credentials in n/a

> Remote attackers can execute arbitrary code on Qolsys IQ Panels by using hardcoded cryptographic keys to forge digital signatures.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7w76-g22v-gxpg

## What is CVE-2015-6032?

CVE-2015-6032 is a critical vulnerability in n/a, published on 31 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Qolsys IQ Panel (aka QOL) before 1.5.1 has hardcoded cryptographic keys, which allows remote attackers to create digital signatures for code by leveraging knowledge of a key from a different installation.

Weakness: CWE-255

## Which versions are affected by CVE-2015-6032?

It affects 1 product.


Products: Qolsys Iq Panel.

## How do I fix CVE-2015-6032?

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

## Is CVE-2015-6032 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6033](https://insights.sbomify.com/CVE-2015-6033/): Security feature bypass in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6032 and fix it if it is affected.

What it is: CVE-2015-6032 is a critical vulnerability in n/a, published on 31 Oct 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6032 in the wild and no public exploit code.

Affected product: n/a. 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-2015-6032/ (Markdown: https://insights.sbomify.com/CVE-2015-6032/index.md)
```

## Sources

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

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