# CVE-2024-6684: Authentication Bypass in GST Electronics' inohom Nova Panel N7

> Attackers can bypass authentication on the GST Electronics inohom Nova Panel N7, which is now unsupported by the vendor.

- **Severity:** Critical 9.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:N/SA:H/S:P/AU:Y/R:U/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2024
- **Updated:** 3 Jun 2026
- **Also known as:** GHSA-8rqq-pq2c-29q4

## What is CVE-2024-6684?

CVE-2024-6684 is a critical authentication bypass vulnerability in GST Electronics inohom Nova Panel N7, published on 12 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication Bypass Using an Alternate Path or Channel vulnerability in GST Electronics inohom Nova Panel N7 allows Authentication Bypass.

This issue affects inohom Nova Panel N7: through 1.9.9.6. NOTE: The vendor was contacted and it was learned that the product is not supported.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2024-6684 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6684 is a critical authentication bypass vulnerability in GST Electronics inohom Nova Panel N7, published on 12 Aug 2024. 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-2024-6684 in the wild and no public exploit code.

Affected product: GST Electronics inohom Nova Panel N7. 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-6684/ (Markdown: https://insights.sbomify.com/CVE-2024-6684/index.md)
```

## Sources

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

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