CVE-2023-6724
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 vulnerability in Software Engineering Consultancy Machine Equipment Limited Company Hearing Tracking System allows Authentication Abuse. This issue affects Hearing Tracking System: before for IOS 7.0, for Android Latest release 1.0.
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 confidenceThe vulnerability is an Authorization Bypass Through User-Controlled Key in the Hearing Tracking System mobile application. Attackers can manipulate a user-controlled key parameter (likely an object reference or session identifier) to bypass authentication checks and gain unauthorized access to other users' data or administrative functions.
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<= 1.0< 7.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 the installed app versionOpen the Simgesel Hearing Tracking System mobile app, navigate to Settings or About section, and record the version number displayed. On Android, you can also check in Settings > Apps > Hearing Tracking System. On iOS, check in Settings > General > iPhone Storage if the app is installed.Affected if The displayed version is less than 7.0 (or shows version 1.0 or lower)
-
Verify the mobile app is communicating with a backend serverConfigure a network proxy (such as Burp Suite, OWASP ZAP, or Charles Proxy) on a test device to intercept HTTPS traffic from the app. Launch the app and perform typical operations like logging in, viewing hearing data, or accessing user profiles.Affected if The app transmits user identifiers, session tokens, or object references in API request parameters that could be manipulated
-
Check for user-controlled key parameters in API requestsIn the intercepted traffic, examine POST/GET requests for parameters that appear to be direct object references, user IDs, record IDs, or session identifiers. Note any endpoints where these values are sent in plain text or easily guessable formats.Affected if Requests contain parameters like user_id, record_id, session_key, or similar identifiers that are controllable by the user and used for authorization decisions
-
Test for authorization bypassUsing the intercepted requests, modify a user-controlled key parameter (such as changing a user_id or record_id to another value) and replay the request to see if the server returns data belonging to a different user or allows access to unauthorized functions.Affected if The server returns successful responses with data from other users or allows access to functions the current user should not have when key parameters are modified
A defender is affected if the installed Simgesel Hearing Tracking System version is below 7.0 (or version 1.0 or lower) and the app transmits controllable key parameters that can be manipulated to access other users' data.
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 · scoped7.0
Implement proper server-side authorization checks that validate user permissions for every request, avoid relying on user-supplied keys for authorization decisions, and use indirect object references with proper session validation.
iOS: version 7.0 or later; Android: latest version subsequent to 1.0
- 1. Identify the Hearing Tracking System application installed on iOS or Android devices
- 2. For iOS users: Check the current application version in the App Store or device settings
- 3. For iOS users: Update the Hearing Tracking System app to version 7.0 or later from the Apple App Store
- 4. For Android users: Check the current application version in the Google Play Store or device settings
- 5. For Android users: Update the Hearing Tracking System app to the latest available version (subsequent to 1.0) from Google Play Store
- 6. After updating, verify the application functions correctly and test that the authorization bypass vulnerability is no longer exploitable
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6724 — 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-2023-6724 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