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

> An unprivileged attacker can steal personal API keys from users who signed up via social authentication in organizations allowing password auth, leading to account takeover.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 21 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8c73-4mfq-f8m8

## What is CVE-2019-18933?

CVE-2019-18933 is a critical vulnerability in n/a, published on 21 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Zulip Server versions from 1.7.0 to before 2.0.7, a bug in the new user signup process meant that users who registered their account using social authentication (e.g., GitHub or Google SSO) in an organization that also allows password authentication could have their personal API key stolen by an unprivileged attacker, allowing nearly full access to the user's account.

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

It affects 1 product.


Products: Zulip Zulip Server.

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

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

## Is CVE-2019-18933 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15070](https://insights.sbomify.com/CVE-2020-15070/): Code injection in n/a (high 8.8)
- [CVE-2017-0910](https://insights.sbomify.com/CVE-2017-0910/): Missing authorization in Zulip Server (high 8.8)
- [CVE-2025-31478](https://insights.sbomify.com/CVE-2025-31478/): Zulip Authentication Backend Configuration Bypass (high 8.2)
- [CVE-2023-33186](https://insights.sbomify.com/CVE-2023-33186/): Cross-site scripting vulnerability in Zulip Server development branch via topic tooltip (high 8.2)
- [CVE-2024-36612](https://insights.sbomify.com/CVE-2024-36612/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-18933 is a critical vulnerability in n/a, published on 21 Nov 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-18933 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-18933/ (Markdown: https://insights.sbomify.com/CVE-2019-18933/index.md)
```

## Sources

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

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