# CVE-2017-6370: TYPO3 Information Disclosure Vulnerability

> Remote attackers can sniff network traffic to obtain sensitive cleartext user credentials due to insecure HTTP requests triggered by HTTPS referrers.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 17 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-87hc-phmj-rhgh

## What is CVE-2017-6370?

CVE-2017-6370 is a medium-severity vulnerability in Typo3 Typo3, published on 17 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TYPO3 7.6.15 sends an http request to an index.php?loginProvider URI in cases with an https Referer, which allows remote attackers to obtain sensitive cleartext information by sniffing the network and reading the userident and username fields.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2017-6370?

2 open source packages ship an affected version, including typo3/cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | All versions | None |
| `typo3/cms` | Packagist | All versions | None |

Products: Typo3 Typo3.

## How do I fix CVE-2017-6370?

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

## Is CVE-2017-6370 being exploited?

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

Public exploit code:

- TYPO3 v7.6.15 Unencrypted Login Request Assigned CVE Number: CVE-2017-6370 (github_poc): https://github.com/faizzaidi/TYPO3-v7.6.15-Unencrypted-Login-Request

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6370 and fix it if it is affected.

What it is: CVE-2017-6370 is a medium-severity vulnerability in Typo3 Typo3, published on 17 Mar 2017. 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-2017-6370 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected all versions; no fix listed
- typo3/cms (Packagist): affected all versions; no fix listed

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

## Sources

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

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