dbcve.org
Vitrea ViewApplication · Canon

CVE-2022-38765

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-09
Fix available
A fix is available. Upgrade to 7.8 or later.
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
Canon Medical Informatics Vitrea Vision 7.7.76.1 does not adequately enforce access controls. An authenticated user is able to gain unauthorized access to imaging records by tampering with the vitrea-view/studies/search patientId parameter.

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 · high confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in the vitrea-view/studies/search endpoint. An authenticated user can access unauthorized imaging records by tampering with the patientId parameter, indicating a failure to validate that the user has permission to access the specific patient data being requested.

MitigationImplement proper object-level authorization checks to verify the authenticated user has legitimate access to the requested patientId before returning any imaging records. All patient data lookups should validate user permissions against an access control policy.

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
Vitrea ViewApplication
Affected:< 7.8

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 Canon Vitrea View version
    Locate the application version through the system administration interface, about page, or version file typically found in the Vitrea View installation directory. Compare the installed version number against the affected range (versions prior to 7.8).
    Affected if The installed version is Canon Vitrea View below version 7.8
  2. Verify endpoint accessibility
    Confirm that the vitrea-view/studies/search API endpoint is accessible within the environment. This may require reviewing API documentation, network traces, or application routing configuration.
    Affected if The vitrea-view/studies/search endpoint exists and is reachable via the application
  3. Check authentication configuration
    Review the authentication configuration to determine if user sessions are required to access the studies/search endpoint. Verify whether the endpoint accepts and processes authenticated requests.
    Affected if The endpoint accepts authenticated requests without requiring additional object-level authorization validation
  4. Test authorization boundary
    Using an authenticated session with known patient access permissions, submit a request to vitrea-view/studies/search with a patientId parameter value for a different patient to which the authenticated user should not have access. Observe whether the application returns imaging records for the unauthorized patientId.
    Affected if The application returns imaging records for patientId values that the authenticated user is not authorized to access

The environment is affected if Canon Vitrea View version is below 7.8 and the studies/search endpoint permits access to patient records without proper authorization validation on the patientId parameter.

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
Upgrade available Upgrade to 7.8 or later
Fixed in 7.8
Interim mitigation

Implement proper object-level authorization checks to verify the authenticated user has legitimate access to the requested patientId before returning any imaging records. All patient data lookups should validate user permissions against an access control policy.

Recommended fix Moderate confidence

Vitrea View 7.8 or later

  1. Contact Canon Medical Informatics customer support to obtain the Vitrea View 7.8 upgrade package
  2. Schedule a maintenance window for the upgrade
  3. Backup the current Vitrea View configuration and database
  4. Follow Canon Medical Informatics official upgrade documentation to install version 7.8
  5. After upgrade, verify that the vitrea-view/studies/search endpoint now properly enforces authorization checks
  6. Test that users can only access imaging records they are authorized to view
Caveat Medical software upgrades may require validation; coordinate with clinical stakeholders and verify compatibility with integrated systems

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

Fix this in Vitrea View Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38765 — 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-38765 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