# CVE-2018-1000123: Information disclosure in n/a

> Attackers with access to iOS logs can read sensitive login and password data leaked by the Cordova iOS Keychain plugin.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 13 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-q5qj-42fq-523r

## What is CVE-2018-1000123?

CVE-2018-1000123 is a critical vulnerability in n/a, published on 13 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ionic Team Cordova plugin iOS Keychain version before commit 18233ca25dfa92cca018b9c0935f43f78fd77fbf contains an Information Exposure Through Log Files (CWE-532) vulnerability in CDVKeychain.m that can result in login, password and other sensitive data leakage. This attack appear to be exploitable via Attacker must have access to victim's iOS logs. This vulnerability appears to have been fixed in after commit 18233ca25dfa92cca018b9c0935f43f78fd77fbf.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2018-1000123?

It affects 1 product.


Products: Ionicframework Ios Keychain.

## How do I fix CVE-2018-1000123?

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

## Is CVE-2018-1000123 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000123 and fix it if it is affected.

What it is: CVE-2018-1000123 is a critical vulnerability in n/a, published on 13 Mar 2018. 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-2018-1000123 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-2018-1000123/ (Markdown: https://insights.sbomify.com/CVE-2018-1000123/index.md)
```

## Sources

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

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