# CVE-2023-28727: Auth bypass in AiSEG2

> Adjacent attackers can bypass authentication in Panasonic AiSEG2 systems by manipulating X-Forwarded-For headers.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/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:** 31 Mar 2023
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-cqq6-v7j5-vr3p

## What is CVE-2023-28727?

CVE-2023-28727 is a critical authentication bypass vulnerability in Panasonic AiSEG2, published on 31 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Panasonic AiSEG2 versions 2.00J through 2.93A allows adjacent attackers bypass authentication due to mishandling of X-Forwarded-For headers.

Weakness: CWE-287 (Improper Authentication), CWE-305 (Authentication Bypass by Primary Weakness)

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

It affects 1 product.


Products: Panasonic Aiseg2 Firmware.

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

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

## Is CVE-2023-28727 being exploited?

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

## Other vulnerabilities in Panasonic AiSEG2

- [CVE-2023-28726](https://insights.sbomify.com/CVE-2023-28726/): Command injection in AiSEG2 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-28727 is a critical authentication bypass vulnerability in Panasonic AiSEG2, published on 31 Mar 2023. 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-2023-28727 in the wild and no public exploit code.

Affected product: Panasonic AiSEG2. 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-28727/ (Markdown: https://insights.sbomify.com/CVE-2023-28727/index.md)
```

## Sources

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

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