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

> An attacker with local access can read sensitive credentials from log files generated by the password manager when interacting with Safari.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x6pq-9vmv-rcjm

## What is CVE-2018-19863?

CVE-2018-19863 is a medium-severity vulnerability in n/a, published on 22 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in 1Password 7.2.3.BETA before 7.2.3.BETA-3 on macOS. A mistake in error logging resulted in instances where sensitive data passed from Safari to 1Password could be logged locally on the user's machine. This data could include usernames and passwords that a user manually entered into Safari.

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

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

It affects 1 product.


Products: Agilebits 1password.

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

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

## Is CVE-2018-19863 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19863 is a medium-severity vulnerability in n/a, published on 22 Dec 2018. 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-2018-19863 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-19863/ (Markdown: https://insights.sbomify.com/CVE-2018-19863/index.md)
```

## Sources

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

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