CVE-2024-48798 Information disclosure in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2024-48798 and fix it if it is affected.
What it is: CVE-2024-48798 is a high-severity vulnerability in n/a, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48798 exists.
Affected product: n/a. 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-48798/ (Markdown: https://insights.sbomify.com/CVE-2024-48798/index.md)
A remote attacker can obtain sensitive information through the firmware update process in the Hubble Connected mobile application.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-48798?
CVE-2024-48798 is a high-severity vulnerability in n/a, published on 14 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An issue in Hubble Connected (com.hubbleconnected.vervelife) 2.00.81 allows a remote attacker to obtain sensitive information via the firmware update process.
Weakness: CWE-200
Which versions are affected by CVE-2024-48798?
How do I fix CVE-2024-48798?
No fix has been published for CVE-2024-48798 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-48798 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-48798 exists.
Sources
Also known as GHSA-3jr7-qfmv-8m22.