# CVE-2023-7007: CVE-2023-7007

> Attackers can impersonate the GatewayG2 to obtain the unlockKey due to missing connection validation in the Sciener server.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-f44j-2w83-q5cc

## What is CVE-2023-7007?

CVE-2023-7007 is a high-severity authentication bypass vulnerability in Sciener Gateway G2, published on 15 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sciener server does not validate connection requests from the GatewayG2, allowing an impersonation attack that provides the attacker the unlockKey field.

## Which versions are affected by CVE-2023-7007?


## How do I fix CVE-2023-7007?

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

## Is CVE-2023-7007 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7007 and fix it if it is affected.

What it is: CVE-2023-7007 is a high-severity authentication bypass vulnerability in Sciener Gateway G2, published on 15 Mar 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-2023-7007 in the wild and no public exploit code.

Affected product: Sciener Gateway G2. 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-2023-7007/ (Markdown: https://insights.sbomify.com/CVE-2023-7007/index.md)
```

## Sources

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

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