# CVE-2023-23131: Weak cryptography in n/a

> An attacker can intercept or modify traffic due to insecure App Transport Security settings in the Selfwealth iOS app.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2023
- **Updated:** 27 Mar 2025
- **Also known as:** GHSA-pvg4-2wp8-hx6g

## What is CVE-2023-23131?

CVE-2023-23131 is a high-severity vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Selfwealth iOS mobile App 3.3.1 is vulnerable to Insecure App Transport Security (ATS) Settings.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2023-23131?

It affects 1 product.


Products: Selfwealth Selfwealth.

## How do I fix CVE-2023-23131?

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

## Is CVE-2023-23131 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-23132](https://insights.sbomify.com/CVE-2023-23132/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23131 and fix it if it is affected.

What it is: CVE-2023-23131 is a high-severity vulnerability in n/a, published on 1 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-23131 in the wild and no public exploit code.

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-2023-23131/ (Markdown: https://insights.sbomify.com/CVE-2023-23131/index.md)
```

## Sources

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

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