# CVE-2018-17502: Information disclosure in The Receptionist for iPad

> A local attacker can access sensitive contact information stored in the application's configuration file.

- **Severity:** Medium 4.0 (`CVSS:3.0/PR:N/A:N/AV:L/I:N/S:U/UI:N/AC:L/C:L/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5hhf-xggq-xjwj

## What is CVE-2018-17502?

CVE-2018-17502 is a medium-severity vulnerability in Los Trigos, Inc The Receptionist for iPad, published on 19 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Receptionist for iPad could allow a local attacker to obtain sensitive information, caused by an error in the contact.json file. An attacker could exploit this vulnerability to obtain the contact names, phone numbers and emails.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Thereceptionist the Receptionist for Ipad.

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

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

## Is CVE-2018-17502 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17502 is a medium-severity vulnerability in Los Trigos, Inc The Receptionist for iPad, published on 19 Mar 2019. 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-17502 in the wild and no public exploit code.

Affected product: Los Trigos, Inc The Receptionist for iPad. 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-17502/ (Markdown: https://insights.sbomify.com/CVE-2018-17502/index.md)
```

## Sources

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

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