# CVE-2019-9744: Auth bypass in n/a

> Attackers can hijack sessions and access the web interface by sharing an IP address with an authenticated user on PHOENIX CONTACT devices.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p5mw-x2jr-q9g7

## What is CVE-2019-9744?

CVE-2019-9744 is a high-severity authentication bypass vulnerability in n/a, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered on PHOENIX CONTACT FL NAT SMCS 8TX, FL NAT SMN 8TX, FL NAT SMN 8TX-M, and FL NAT SMN 8TX-M-DMG devices. There is unauthorized access to the WEB-UI by attackers arriving from the same source IP address as an authenticated user, because this IP address is used as a session identifier.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2019-9744?

It affects 4 products.


Products: Phoenixcontact Fl Nat Smcs 8tx Firmware, Phoenixcontact Fl Nat Smn 8tx-M-Dmg Firmware, Phoenixcontact Fl Nat Smn 8tx-M Firmware, Phoenixcontact Fl Nat Smn 8tx Firmware.

## How do I fix CVE-2019-9744?

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

## Is CVE-2019-9744 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9744 and fix it if it is affected.

What it is: CVE-2019-9744 is a high-severity authentication bypass vulnerability in n/a, published on 26 Mar 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-9744 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-2019-9744/ (Markdown: https://insights.sbomify.com/CVE-2019-9744/index.md)
```

## Sources

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

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