# CVE-2023-36144: Auth bypass in n/a

> An unauthenticated attacker can bypass authentication to download device backups, exposing critical configuration information on Intelbras switches.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 30 Jun 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-jgg8-69rp-g5j5

## What is CVE-2023-36144?

CVE-2023-36144 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass in Intelbras Switch SG 2404 MR in firmware 1.00.54 allows an unauthenticated attacker to download the backup file of the device, exposing critical information about the device configuration.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Intelbras Sg 2404 Mr Firmware.

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

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

## Is CVE-2023-36144 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36144 exists.

Public exploit code:

- https://github.com/leonardobg/CVE-2023-36144 (github_poc): https://github.com/leonardobg/CVE-2023-36144
- Intelbras Switch - Information Disclosure (nuclei): http/cves/2023/CVE-2023-36144.yaml

## Other vulnerabilities in n/a

- [CVE-2022-43308](https://insights.sbomify.com/CVE-2022-43308/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-36144 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-36144 exists.

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-2023-36144/ (Markdown: https://insights.sbomify.com/CVE-2023-36144/index.md)
```

## Sources

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

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