# CVE-2024-48644: Information disclosure in n/a

> Remote attackers can enumerate valid user accounts on Reolink Duo 2 cameras by observing differences in login responses, facilitating further attacks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 22 Oct 2024
- **Updated:** 23 Oct 2024
- **Also known as:** GHSA-xcwc-hmj9-q3x5

## What is CVE-2024-48644?

CVE-2024-48644 is a medium-severity vulnerability in n/a, published on 22 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Accounts enumeration vulnerability in the Login Component of Reolink Duo 2 WiFi Camera (Firmware Version v3.0.0.1889_23031701) allows remote attackers to determine valid user accounts via login attempts. This can lead to the enumeration of user accounts and potentially facilitate other attacks, such as brute-forcing of passwords. The vulnerability arises from the application responding differently to login attempts with valid and invalid usernames.

Weakness: CWE-203 (Observable Discrepancy)

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


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

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

## Is CVE-2024-48644 being exploited?

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

Public exploit code:

- Reolink Duo 2 WiFi v1.0.280 - Account Enumeration Vulnerability (github_poc): https://github.com/rosembergpro/CVE-2024-48644

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48644 is a medium-severity vulnerability in n/a, published on 22 Oct 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-48644 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-48644/ (Markdown: https://insights.sbomify.com/CVE-2024-48644/index.md)
```

## Sources

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

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