CVE-2024-3305
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 · uneditedAuthorization Bypass Through User-Controlled Key, Missing Authorization vulnerability in Utarit Information SoliClub allows Retrieve Embedded Sensitive Data. 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 · high confidenceThis is a missing authorization or authorization bypass vulnerability in the SoliClub mobile application (both iOS and Android versions) that allows attackers to retrieve embedded sensitive data. The vulnerability stems from the application using a user-controlled key to determine which data to access without proper authorization validation, enabling unauthorized access to data that should be protected.
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< 4.4.0< 5.2.1CVSS 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 installed SoliClub version on iOSOpen the App Store, search for SoliClub, tap on the app, and view the version number in the app description. Alternatively, open SoliClub, go to Settings > About to find the version.Affected if The installed version is lower than 4.4.0
-
Identify installed SoliClub version on AndroidOpen the Google Play Store, search for SoliClub, and view the version number in the app listing. Alternatively, go to Settings > Apps > SoliClub on the device to see the version.Affected if The installed version is lower than 5.2.1
-
Compare version against vulnerable rangesIf you have the version number, check the release notes or changelog for SoliClub to confirm whether the specific version you have falls below the patched releases (iOS < 4.4.0, Android < 5.2.1).Affected if Your version falls within the affected ranges: iOS below 4.4.0 or Android below 5.2.1
-
Verify app behavior for unauthorized data access (optional)Since the vulnerability involves user-controlled keys determining data access, review any API traffic or data requests the app makes. If the app allows retrieving other users data by manipulating identifiers in requests, the vulnerability may be present.Affected if The app permits retrieving data belonging to other users by modifying keys or identifiers in requests without proper authorization validation.
You are affected if the SoliClub app version installed on your iOS device is below 4.4.0 or on your Android device is below 5.2.1.
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 · scoped4.4.05.2.1
Upgrade SoliClub to version 4.4.0 or higher for iOS, and version 5.2.1 or higher for Android. These updates contain proper authorization checks to prevent unauthorized data retrieval.
iOS: 4.4.0+; Android: 5.2.1+
- For iOS: Upgrade SoliClub application to version 4.4.0 or later from the official app store
- For Android: Upgrade SoliClub application to version 5.2.1 or later from the official app store
- After upgrading, verify that the application functions correctly and test that the authorization bypass has been remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3305 — 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-2024-3305 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