# CVE-2022-42979: Information disclosure in n/a

> Attackers can disclose information and take over accounts via deep links due to insecure hostname validation in the RYDE mobile application.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Jan 2023
- **Updated:** 9 Apr 2025
- **Also known as:** GHSA-9749-rqrj-vcqj

## What is CVE-2022-42979?

CVE-2022-42979 is a high-severity vulnerability in n/a, published on 6 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Information disclosure due to an insecure hostname validation in the RYDE application 5.8.43 for Android and iOS allows attackers to take over an account via a deep link.

Weakness: CWE-295 (Improper Certificate Validation), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-42979?

It affects 1 product.


Products: Rydesharing Ryde.

## How do I fix CVE-2022-42979?

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

## Is CVE-2022-42979 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-42979 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-42979 and fix it if it is affected.

What it is: CVE-2022-42979 is a high-severity vulnerability in n/a, published on 6 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-42979 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-2022-42979/ (Markdown: https://insights.sbomify.com/CVE-2022-42979/index.md)
```

## Sources

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

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