# CVE-2019-19739: Information disclosure in n/a

> Attackers can intercept session cookies sent over unencrypted channels, potentially leading to account takeover or data exposure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 30 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-66vr-9fmp-3692

## What is CVE-2019-19739?

CVE-2019-19739 is a high-severity vulnerability in n/a, published on 30 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MFScripts YetiShare 3.5.2 through 4.5.3 does not set the Secure flag on session cookies, allowing the cookie to be sent over cleartext channels.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

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

It affects 1 product.


Products: Mfscripts Yetishare.

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

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

## Is CVE-2019-19739 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-20062](https://insights.sbomify.com/CVE-2019-20062/): Auth bypass in n/a (critical 9.8)
- [CVE-2019-19735](https://insights.sbomify.com/CVE-2019-19735/): Weak cryptography in n/a (critical 9.1)
- [CVE-2019-20059](https://insights.sbomify.com/CVE-2019-20059/): SQL injection in n/a (high 8.8)
- [CVE-2019-19734](https://insights.sbomify.com/CVE-2019-19734/): SQL injection in n/a (high 8.8)
- [CVE-2019-19737](https://insights.sbomify.com/CVE-2019-19737/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19739 is a high-severity vulnerability in n/a, published on 30 Dec 2019. 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-2019-19739 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-19739/ (Markdown: https://insights.sbomify.com/CVE-2019-19739/index.md)
```

## Sources

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

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