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

> An attacker can send arbitrary in-game push notifications to users because the Android app lacks authorization checks on its broadcast receiver.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cc2v-347v-c452

## What is CVE-2020-25204?

CVE-2020-25204 is a medium-severity missing authorization vulnerability in n/a, published on 28 Oct 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The God Kings application 0.60.1 for Android exposes a broadcast receiver to other apps called com.innogames.core.frontend.notifications.receivers.LocalNotificationBroadcastReceiver. The purpose of this broadcast receiver is to show an in-game push notification to the player. However, the application does not enforce any authorization schema on the broadcast receiver, allowing any application to send fully customizable in-game push notifications.

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

It affects 1 product.


Products: Innogames God Kings.

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

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

## Is CVE-2020-25204 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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