dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-33309

HIGH · 7.5 CVSS v3.1 Published 2024-04-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
An issue in TVS Motor Company Limited TVS Connet Android v.4.5.1 and iOS v.5.0.0 allows a remote attacker to obtain sensitive information via an insecure API endpoint. NOTE: this is disputed as discussed in the msn-official/CVE-Evidence repository.

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 confidence

The TVS Connet mobile application (Android v4.5.1 and iOS v5.0.0) contains an insecure API endpoint that allows unauthenticated remote attackers to retrieve sensitive information without proper authentication or authorization controls.

MitigationSecure the API endpoint by implementing proper authentication (e.g., OAuth 2.0), role-based authorization checks, and ensuring all API communications occur over HTTPS with appropriate input validation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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 if TVS Connect app is installed on Android
    Open device Settings > Apps > TVS Connect, or use ADB command: adb shell pm list packages | grep -i tvs
    Affected if TVS Connect package is found on the device
  2. Identify if TVS Connect app is installed on iOS
    Open Settings > TVS Connect, or use Xcode command: idevicesyslog | grep -i tvs, or check via iTunes/Finder
    Affected if TVS Connect app is found on the device
  3. Determine installed Android app version
    Navigate to Settings > Apps > TVS Connect > App info, or use ADB: adb shell dumpsys package com.tvsconnect | grep versionName
    Affected if Version is Android v4.5.1 (the affected version)
  4. Determine installed iOS app version
    Open App Store > TVS Connect > App version, or go to Settings > TVS Connect > Version
    Affected if Version is iOS v5.0.0 (the affected version)
  5. Verify API endpoint accessibility (if applicable)
    Use a network proxy (e.g., Burp Suite, mitmproxy) to intercept app traffic and check if requests to the TVS Connect API endpoint lack authentication headers or tokens
    Affected if API requests succeed without valid authentication credentials

User is affected if TVS Connect app (Android v4.5.1 or iOS v5.0.0) is installed and communicates with the insecure API endpoint without proper authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Secure the API endpoint by implementing proper authentication (e.g., OAuth 2.0), role-based authorization checks, and ensuring all API communications occur over HTTPS with appropriate input validation.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-33309 — 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-2024-33309 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