Uber's disclosed vulnerabilities center on a narrow set of internal and customer-facing platforms, including its Kraken infrastructure component and UberEats application, with the signal characterized by path-traversal and hard-coded-credential weaknesses typical of backend systems with inconsistent access control and secret management. Current severity, exploitation, and exposure figures are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Uber over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2017-13104HIGH Uber Technologies, Inc. UberEATS: Uber for Food Delivery, 1.108.10001, 2017-11-02, iOS application uses a hard-coded key for encryption. Data stored using this key can be decrypted | Aug 15, 2018 | 7.5 | 25 | NO | NO |
CVE-2022-47747HIGH kraken <= 0.1.4 has an arbitrary file read vulnerability via the component testfs. | Jan 20, 2023 | 7.5 | 24 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Uber.
Media articles that mention a CVE ID that affects a product developed by Uber — matched by CVE ID, not by vendor name.