dbcve.org
Patient PortalApplication · Lifepoint

CVE-2022-1067

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability combined with broken access control in a healthcare application. The endpoint that generates PDF lab reports accepts a patient ID parameter but does not validate user authentication or session state, allowing any unauthenticated user to access sensitive patient health information (PHI) by simply knowing or guessing valid patient IDs.

MitigationImplement robust authentication and session validation on the lab report PDF generation endpoint, combined with proper authorization checks to ensure users can only access reports they're permitted to view. Consider adding rate limiting as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Patient PortalApplication
Affected:< lpi_3.5.12.p30

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Lifepoint Patient Portal installation
    Locate the Lifepoint Patient Portal web application in your environment. Search for files, directories, or services matching 'lpi', 'lifepoint', or 'patient-portal' naming conventions.
    Affected if The application is present in your environment
  2. Determine installed version
    Check the application version by reviewing configuration files, about pages, version manifests, or headers. Compare against the affected range: versions before lpi_3.5.12.p30 are vulnerable.
    Affected if Installed version is lpi_3.5.12.p29 or earlier (any version below lpi_3.5.12.p30)
  3. Locate lab report PDF generation endpoint
    Identify the web endpoint that generates PDF lab reports. Review application URLs, routes, or web server access logs for patterns containing 'pdf', 'report', 'lab', or 'patient' parameters.
    Affected if The lab report PDF endpoint exists and accepts a patient ID parameter
  4. Test unauthenticated access to the endpoint
    Send a direct HTTP request to the PDF generation endpoint with a patient ID parameter without providing any authentication credentials or session cookies. Example: curl -v 'http://<host>/<path>?patient_id=<any_id>'
    Affected if The endpoint returns a PDF without requiring authentication or session validation

Your environment is affected if the Lifepoint Patient Portal version is below lpi_3.5.12.p30 and the lab report PDF endpoint can be accessed without authentication, allowing unauthorized disclosure of patient health information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust authentication and session validation on the lab report PDF generation endpoint, combined with proper authorization checks to ensure users can only access reports they're permitted to view. Consider adding rate limiting as a defense-in-depth measure.

Recommended fix High confidence

lpi_3.5.12.p30 or later

  1. Identify current Patient Portal version by checking software build or configuration
  2. Review release notes for version lpi_3.5.12.p30 to understand security fixes and any changes
  3. Perform a full backup of the Patient Portal application and associated database
  4. Upgrade Patient Portal to version lpi_3.5.12.p30 or later
  5. Verify the authentication bypass vulnerability is resolved by attempting to access the vulnerable URL without credentials
  6. Confirm normal authentication and authorization controls are functioning properly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Patient Portal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1067 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data