# CVE-2020-5532: Auth bypass in ilbo App

> An attacker on the same network can bypass authentication to view images recorded by other users' devices in the ilbo mobile application.

- **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:** 14 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2jvm-wg52-7h4f

## What is CVE-2020-5532?

CVE-2020-5532 is a medium-severity authentication bypass vulnerability in EXTRUN Ltd. ilbo App, published on 14 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ilbo App (ilbo App for Android prior to version 1.1.8 and ilbo App for iOS prior to version 1.2.01) allows an attacker on the same network segment to bypass authentication and to view the images which were recorded by the other ilbo user's device via unspecified vectors.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Extrun Ilbo.

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

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

## Is CVE-2020-5532 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-5532 is a medium-severity authentication bypass vulnerability in EXTRUN Ltd. ilbo App, published on 14 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-5532 in the wild and no public exploit code.

Affected product: EXTRUN Ltd. ilbo App. 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-5532/ (Markdown: https://insights.sbomify.com/CVE-2020-5532/index.md)
```

## Sources

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

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