# CVE-2024-53683: Ossur Mobile Logic Application Exposure of Sensitive System Information to an Unauthorized Control Sphere

> Attackers can extract hardcoded credentials and tokens from the mobile app to disrupt operations and modify translation files.

- **Severity:** Medium 5.6 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-vq45-v67f-g42p

## What is CVE-2024-53683?

CVE-2024-53683 is a medium-severity vulnerability in Ossur Mobile Logic Application, published on 17 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A valid set of credentials in a .js file and a static token for 
communication were obtained from the decompiled IPA. An attacker could 
use the information to disrupt normal use of the application by changing
 the translation files and thus weaken the integrity of normal use.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2024-53683?


## How do I fix CVE-2024-53683?

No fix has been published for CVE-2024-53683 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-53683 being exploited?

There is no known exploitation of CVE-2024-53683 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53683 and fix it if it is affected.

What it is: CVE-2024-53683 is a medium-severity vulnerability in Ossur Mobile Logic Application, published on 17 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-53683 in the wild and no public exploit code.

Affected product: Ossur Mobile Logic Application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-53683/ (Markdown: https://insights.sbomify.com/CVE-2024-53683/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-53683
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-53683
- OSV: https://osv.dev/vulnerability/CVE-2024-53683

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-53683/
Summaries are generated and may contain mistakes; the official description above is the record.