# CVE-2022-34775: Tabit - Excessive data exposure

> Attackers can retrieve sensitive customer data including contact details and spending history via an exposed API endpoint, facilitating phishing attacks.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-cqvg-fwrm-3xxf

## What is CVE-2022-34775?

CVE-2022-34775 is a medium-severity vulnerability in Tabit, published on 22 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tabit - Excessive data exposure. Another endpoint mapped by the tiny url, was one for reservation cancellation, containing the MongoDB ID of the reservation, and organization. This can be used to query the http://tgm-api.tabit.cloud/rsv/management/{reservationId}?organization={orgId} API which returns a lot of data regarding the reservation (OWASP: API3): Name, mail, phone number, the number of visits of the user to this specific restaurant, the money he spent there, the money he spent on alcohol, whether he left a deposit etc. This information can easily be used for a phishing attack.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2022-34775?

It affects 1 product.


Products: Tabit Tabit.

## How do I fix CVE-2022-34775?

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

## Is CVE-2022-34775 being exploited?

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

## Other vulnerabilities in Tabit

- [CVE-2022-34774](https://insights.sbomify.com/CVE-2022-34774/): Tabit - Arbitrary account modification (medium 6.3)
- [CVE-2022-34771](https://insights.sbomify.com/CVE-2022-34771/): Tabit - arbitrary SMS send on Tabits behalf (medium 5.5)
- [CVE-2022-34776](https://insights.sbomify.com/CVE-2022-34776/): Tabit - giftcard stealth (medium 5.5)
- [CVE-2022-34773](https://insights.sbomify.com/CVE-2022-34773/): Tabit - HTTP Method manipulation (medium 4.9)
- [CVE-2022-34770](https://insights.sbomify.com/CVE-2022-34770/): Tabit - sensitive information disclosure (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34775 and fix it if it is affected.

What it is: CVE-2022-34775 is a medium-severity vulnerability in Tabit, published on 22 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34775 in the wild and no public exploit code.

Affected product: Tabit. 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-2022-34775/ (Markdown: https://insights.sbomify.com/CVE-2022-34775/index.md)
```

## Sources

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

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