# CVE-2020-28713: Missing authorization in n/a

> Remote attackers can bypass authentication to record or flood push notifications on Night Owl Smart Doorbells, causing privacy leaks and service disruption.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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:** 8 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w273-hj4m-f2f7, UBUNTU-CVE-2020-28713

## What is CVE-2020-28713?

CVE-2020-28713 is a medium-severity missing authorization vulnerability in n/a, published on 8 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in push notification service in Night Owl Smart Doorbell FW version 20190505 allows remote users to send push notification events via an exposed PNS server. A remote attacker can passively record push notification events which are sent over an insecure web request. The web service does not authenticate requests, and allows attackers to send an indefinite amount of motion or doorbell events to a user's mobile application by either replaying or deliberately crafting false events.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: Nightowlsp Smart Doorbell Firmware.

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

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

## Is CVE-2020-28713 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-28713 is a medium-severity missing authorization vulnerability in n/a, published on 8 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28713 in the wild and no public exploit code.

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

## Sources

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

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