SoliclubApplication · Utarit

CVE-2024-3306

HIGH · 7.5 CVSS v3.1 Published 2024-09-12
Fix available
A fix is available. Upgrade to 4.4.0 / 5.2.1 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
Authorization Bypass Through User-Controlled Key vulnerability in Utarit Information SoliClub allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects SoliClub: before 4.4.0 for iOS, before 5.2.1 for Android.

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

This is an authorization bypass vulnerability where an attacker can manipulate a user-controlled key parameter to bypass access control checks. The vulnerability stems from incorrectly configured security levels in the access control implementation of the SoliClub mobile application.

MitigationUpgrade SoliClub to version 4.4.0 or higher for iOS and version 5.2.1 or higher for Android to obtain the security fix.

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
SoliclubApplication
Affected:< 4.4.0< 5.2.1

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 the installed SoliClub version on iOS
    Open the App Store app, go to your profile, tap 'Purchased', find SoliClub, and note the version number shown. Alternatively, check the app version in Settings > Apps > SoliClub (depending on iOS version).
    Affected if The version is lower than 4.4.0
  2. Identify the installed SoliClub version on Android
    Open the Google Play Store app, search for 'Utarit Soliclub', tap on the app, and note the current version shown under the app name. Alternatively, go to Settings > Apps > SoliClub on the device.
    Affected if The version is lower than 5.2.1
  3. Confirm the app is the genuine Utarit Soliclub application
    Verify the app developer/package name matches 'Utarit' or the official publisher. On Android, check Package Name in Settings > Apps > SoliClub. On iOS, check the developer name in the App Store listing.
    Affected if The app is from the official Utarit developer and the version falls within affected ranges
  4. Determine if user authentication and access control features are in use
    Launch SoliClub and log in with a user account. Navigate to any feature that involves accessing restricted data or performing privileged actions.
    Affected if The app executes any authenticated operations, as the vulnerability allows bypassing access control during such operations

A user is affected if they have SoliClub installed with version below 4.4.0 on iOS or below 5.2.1 on Android, and the app is actively used for authenticated operations where access control could be bypassed.

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 4.4.0 / 5.2.1 or later
Fixed in 4.4.05.2.1
Interim mitigation

Upgrade SoliClub to version 4.4.0 or higher for iOS and version 5.2.1 or higher for Android to obtain the security fix.

Recommended fix High confidence

iOS: 4.4.0+, Android: 5.2.1+

  1. For iOS devices: Upgrade SoliClub application to version 4.4.0 or later from the official App Store
  2. For Android devices: Upgrade SoliClub application to version 5.2.1 or later from the official Google Play Store
  3. After upgrading, verify the application version matches or exceeds the fixed releases (iOS: 4.4.0+, Android: 5.2.1+)

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

Fix this in Soliclub 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-2024-3306 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3306 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