CVE-2022-34770
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 - sensitive information disclosure. Several APIs on the web system display, without authorization, sensitive information such as health statements, previous bills in a specific restaurant, alcohol consumption and smoking habits. Each of the described API’s, has in its URL one or more MongoDB ID which is not so simple to enumerate. However, they each receive a ‘tiny URL’ in Tabit’s domain, in the form of https://tbit.be/{suffix} with suffix being a 5 characters long string containing numbers, lower- and upper-case letters. It is not so simple to enumerate them all, but really easy to find some that work and lead to a personal endpoint. This is both an example of OWASP: API4 - rate limiting and OWASP: API1 - Broken object level authorization. Furthermore, the redirect URL disclosed the MongoDB IDs discussed above, and we could use them to query other endpoints disclosing more personal information. For example: The URL https://tabitisrael.co.il/online-reservations/health-statement?orgId={org_id}&healthStatementId={health_statement_id} is used to invite friends to fill a health statement before attending the restaurant. We can use the health_statement_id to access the https://tgm-api.tabit.cloud/health-statement/{health_statement_id} API which disclose medical information as well as id number.
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 · high confidenceThe Tabit web application has multiple API endpoints that expose sensitive personal data (health statements, restaurant bills, medical information, ID numbers) without proper authorization. The vulnerability stems from predictable short URLs (5-character suffixes) that redirect to endpoints containing MongoDB IDs, which can then be used to access additional personal data through other APIs. This is both an IDOR (Broken Object Level Authorization) and rate limiting issue per OWASP classifications.
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 web application installationCheck the application's version banner, about page, or API response headers for version information. For web deployments, inspect the main page source or check /api/version endpoint if available.Affected if Version is displayed and is below 3.27.0
-
Enumerate short URL patternsAttempt to access the redirect mechanism by testing common 5-character suffix patterns (e.g., /r/abcde). Check if the application returns HTTP redirects to endpoints containing MongoDB ObjectIDs in the URL.Affected if Short URLs redirect to endpoints containing 24-character hexadecimal strings resembling MongoDB ObjectIDs
-
Test authorization on redirect targetsAccess the redirect target URL directly (containing the MongoDB ID) without authentication or with a low-privilege account. Attempt to retrieve sensitive data such as health statements, restaurant bills, medical records, or ID numbers.Affected if Sensitive personal data is returned without requiring proper authorization
-
Attempt ID enumerationSystematically vary the MongoDB ID portion in API endpoints to access records belonging to other users. Test multiple sequential or adjacent ID values to see if data from different user accounts is accessible.Affected if Different user data is returned when modifying the ID parameter, indicating broken object-level authorization
-
Check for rate limitingSend multiple rapid requests to the short URL redirect endpoint or API endpoints exposing personal data. Observe if the application throttles or blocks repeated requests.Affected if No rate limiting is enforced and enumeration of multiple IDs is possible without blocking
A system is affected if it runs Tabit version below 3.27.0 and exposes personal data through predictable short URLs or MongoDB ID-based API endpoints without proper authorization checks.
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 proper authorization checks on all API endpoints verifying the requesting user has rights to access the requested data, add rate limiting to prevent enumeration of short URLs and IDs, and remove sensitive MongoDB IDs from redirect URLs by using indirect references.
Tabit 3.27.0
- Verify current Tabit version by checking the system administration panel or contacting system administrator
- Contact Tabit vendor support and request upgrade to version 3.27.0 or later to address the IDOR vulnerability
- Confirm with vendor that the fix includes proper authorization checks on all sensitive endpoints (/health-statement, /bills, etc.
- After upgrade, verify that access to personal health statements, bills, and medical information requires proper authentication
- Test that direct URL access with MongoDB IDs no longer returns sensitive data without authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.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 $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34770 — 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-34770 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