# CVE-2022-1067: ICSMA-22-095-01 LifePoint Informatics Patient Portal

> Unauthenticated attackers can access sensitive patient lab reports by navigating to specific URLs, exposing private health information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2022
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-9wgg-qjjm-45vr

## What is CVE-2022-1067?

CVE-2022-1067 is a medium-severity missing authorization vulnerability in LifePoint Informatics Patient Portal, published on 11 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Navigating to a specific URL with a patient ID number will result in the server generating a PDF of a lab report without authentication and rate limiting.

Weakness: CWE-287 (Improper Authentication), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Lifepoint Patient Portal.

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

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

## Is CVE-2022-1067 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1067 is a medium-severity missing authorization vulnerability in LifePoint Informatics Patient Portal, published on 11 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1067 in the wild and no public exploit code.

Affected product: LifePoint Informatics Patient Portal. 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-1067/ (Markdown: https://insights.sbomify.com/CVE-2022-1067/index.md)
```

## Sources

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

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