# CVE-2020-11447: Information disclosure in n/a

> Remote authenticated users can retrieve the device serial number, leaking information intended to verify physical access.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2023
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-4xfh-r54g-8ff7

## What is CVE-2020-11447?

CVE-2020-11447 is a medium-severity vulnerability in n/a, published on 17 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Bell HomeHub 3000 SG48222070 devices. Remote authenticated users can retrieve the serial number via cgi/json-req - this is an information leak because the serial number is intended to prove an actor's physical access to the device.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2020-11447?

It affects 1 product.


Products: Bell Home Hub 3000 Firmware.

## How do I fix CVE-2020-11447?

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

## Is CVE-2020-11447 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11448](https://insights.sbomify.com/CVE-2020-11448/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11447 and fix it if it is affected.

What it is: CVE-2020-11447 is a medium-severity vulnerability in n/a, published on 17 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-11447 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-2020-11447/ (Markdown: https://insights.sbomify.com/CVE-2020-11447/index.md)
```

## Sources

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

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