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

> Attackers on public Wi-Fi can intercept authentication credentials and user passwords via man-in-the-middle attacks due to insecure session validation.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-722f-77g4-vmm4

## What is CVE-2020-23036?

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

### Official description

MEDIA NAVI Inc SMACom v1.2 was discovered to contain an insecure session validation vulnerability in the session handling of the `password` authentication parameter of the wifi photo transfer module. This vulnerability allows attackers with network access privileges or on public wifi networks to read the authentication credentials and follow-up requests containing the user password via a man in the middle attack.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Medianavi Smacom.

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

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

## Is CVE-2020-23036 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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