# CVE-2023-2504: Hardcoded credentials in 4K QUAD

> Attackers can gain root access to BirdDog video cameras using hard-coded credentials found in firmware images.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/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:** 22 May 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-q93p-3qj2-8qc8

## What is CVE-2023-2504?

CVE-2023-2504 is a high-severity vulnerability in BirdDog 4K QUAD, published on 22 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Files present on firmware images could allow an attacker to gain unauthorized access as a root user using hard-coded credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 4 products.


Products: Birddog 4k Quad Firmware, Birddog A300 Firmware, Birddog Mini Firmware, Birddog Studio R3 Firmware.

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

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

## Is CVE-2023-2504 being exploited?

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

## Other vulnerabilities in BirdDog 4K QUAD

- [CVE-2023-2505](https://insights.sbomify.com/CVE-2023-2505/): Cross-site request forgery in 4K QUAD (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-2504 is a high-severity vulnerability in BirdDog 4K QUAD, published on 22 May 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-2504 in the wild and no public exploit code.

Affected product: BirdDog 4K QUAD. 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-2504/ (Markdown: https://insights.sbomify.com/CVE-2023-2504/index.md)
```

## Sources

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

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