dbcve.org
TabitApplication

CVE-2022-34776

HIGH · 7.5 CVSS v3.1 Published 2022-08-22
Fix available
A fix is available. Upgrade to 3.27.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Tabit - giftcard stealth. 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 APIs, has in its URL one or more MongoDB ID which is not so simple to enumerate. However, they each receive a 'tiny URL' in tabits domain, in the form of https://tbit.be/{suffix} with suffix being a 5 character 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. Furthermore, the redirect URL disclosed the MongoDB IDs discussed above, and we could use them to query other endpoints disclosing more personal information.

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 confidence

IDOR (Insecure Direct Object Reference) vulnerability in Tabit giftcard APIs allowing unauthenticated access to sensitive PII including health statements, restaurant bills, and alcohol/smoking habits. The APIs use MongoDB IDs protected by weak 5-character alphanumeric 'tiny URLs' that leak in redirect responses, enabling enumeration and unauthorized access to personal endpoints.

MitigationImplement proper authentication and role-based authorization checks on all API endpoints, remove MongoDB ID leakage from redirect URLs, and strengthen or replace the tiny URL mechanism with proper session-based access controls.

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
TabitApplication
Affected:< 3.27.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tabit installation
    Locate the Tabit application in your environment - this could be a web application, mobile backend, or hosted service. Check application metadata, headers, or configuration files for 'Tabit' branding or references.
    Affected if Tabit is present in your environment
  2. Determine installed Tabit version
    Check the application's version information through admin panels, configuration files, API response headers, or the application's /about/info endpoint if available. Compare against the affected range: versions prior to 3.27.0.
    Affected if Installed version is lower than 3.27.0
  3. Locate giftcard API endpoints
    Identify if giftcard-related API endpoints exist in your Tabit deployment. Common paths may include /giftcard, /api/giftcard, or similar variations. Check API documentation or route configurations.
    Affected if Giftcard API endpoints are accessible in your Tabit deployment
  4. Check for tiny URL mechanism in redirects
    Make a test request to any giftcard endpoint and observe redirect responses. Look for 5-character alphanumeric strings (tiny IDs) appearing in Location headers or redirect URLs.
    Affected if Redirects contain 5-character alphanumeric codes that could be enumerated

You are affected if you are running Tabit version lower than 3.27.0 with exposed giftcard API endpoints that leak short alphanumeric IDs in redirect responses.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.27.0 or later
Fixed in 3.27.0
Interim mitigation

Implement proper authentication and role-based authorization checks on all API endpoints, remove MongoDB ID leakage from redirect URLs, and strengthen or replace the tiny URL mechanism with proper session-based access controls.

Recommended fix High confidence

Tabit version 3.27.0 or later

  1. Identify all Tabit instances currently running versions prior to 3.27.0 in your environment
  2. Review the Tabit 3.27.0 release notes and changelog for any configuration or API changes
  3. Create a backup of the current Tabit deployment including database and configuration files
  4. Test the upgrade in a non-production environment to verify compatibility
  5. Schedule a maintenance window for the production upgrade
  6. Upgrade Tabit to version 3.27.0 or the latest stable release that includes the fix
  7. Verify that the sensitive information exposure vulnerability is resolved by testing the affected API endpoints
  8. Confirm that the 'tiny URL' redirects no longer expose MongoDB IDs in the response headers or body
Caveat Review release notes for any breaking changes between your current version and 3.27.0; test thoroughly in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tabit Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34776 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34776 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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