CVE-2022-34775
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTabit - 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Tabit reservation management API at tgm-api.tabit.cloud exposes sensitive customer data (names, emails, phone numbers, visit history, spending amounts, deposit status) without proper authorization. Attackers can retrieve this PII by querying the /rsv/management/{reservationId} endpoint with only a reservation MongoDB ID and organization ID, representing OWASP API3:2019 (Excessive Data Exposure).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.27.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Tabit reservation system usageConfirm your organization uses Tabit software or API services for reservation management. Check if your systems integrate with tgm-api.tabit.cloud or if Tabit is listed in your vendor/inventory records.Affected if Tabit reservation management is in use and the version is unknown or below 3.27.0
-
Determine installed Tabit versionLocate the Tabit software version number through your vendor documentation, admin panel, or system inventory. If using the hosted cloud service, contact Tabit support to confirm your deployment version.Affected if Version is below 3.27.0 or cannot be verified
-
Test endpoint authorization with reservation IDQuery the /rsv/management/{reservationId} endpoint using a reservation MongoDB ID and organization ID. Attempt this with credentials from one user/reservation while trying to access data from another user/reservation.Affected if API returns PII (names, emails, phone numbers, visit history, spending amounts, deposit status) for reservations that do not belong to the requesting user or organization
-
Inspect API response fields for data exposureCapture and review the full JSON response from the /rsv/management/{reservationId} endpoint. Examine whether the response contains fields beyond operationally necessary data, including customer full names, email addresses, phone numbers, visit history, spending totals, and deposit status.Affected if API response includes sensitive PII fields that are not required for the reservation operation being performed
Your environment is affected if you use Tabit reservation management with version below 3.27.0 and the API exposes customer PII to unauthorized users who only possess a reservation ID and organization ID.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.27.0
Implement authorization checks ensuring users can only access their own reservations, and filter API responses to return only operationally necessary fields rather than all available reservation data.
3.27.0
- Upgrade Tabit to version 3.27.0 or later to remediate the IDOR vulnerability.
- After upgrading, verify that the reservation management endpoint no longer returns sensitive data without proper authorization.
- Test that proper authorization checks are now enforced when accessing reservation data via the API.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34775 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data