# CVE-2024-22773: Auth bypass in n/a

> Attackers can bypass login on Intelbras Action RF and RG routers by exploiting exposed passwords in cookies, gaining unauthorized access.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2024
- **Updated:** 5 Jun 2025
- **Also known as:** GHSA-c6f2-5665-5p8p

## What is CVE-2024-22773?

CVE-2024-22773 is a high-severity authentication bypass vulnerability in n/a, published on 6 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Intelbras Action RF 1200 routers 1.2.2 and earlier and Action RG 1200 routers 2.1.7 and earlier expose the Password in Cookie resulting in Login Bypass.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 1 product.


Products: Intelbras Action Rf 1200 Firmware.

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

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

## Is CVE-2024-22773 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19517](https://insights.sbomify.com/CVE-2019-19517/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22773 is a high-severity authentication bypass vulnerability in n/a, published on 6 Feb 2024. 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-2024-22773 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-2024-22773/ (Markdown: https://insights.sbomify.com/CVE-2024-22773/index.md)
```

## Sources

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

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