CVE-2022-39230
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 · uneditedfhir-works-on-aws-authz-smart is an implementation of the authorization interface from the FHIR Works interface. Versions 3.1.1 and 3.1.2 are subject to Exposure of Sensitive Information to an Unauthorized Actor. This issue allows a client of the API to retrieve more information than the client’s OAuth scope permits when making “search-type” requests. This issue would not allow a client to retrieve information about individuals other than those the client was already authorized to access. Users of fhir-works-on-aws-authz-smart 3.1.1 or 3.1.2 should upgrade to version 3.1.3 or higher immediately. Versions 3.1.0 and below are unaffected. There is no workaround for this issue.
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 confidencefhir-works-on-aws-authz-smart versions 3.1.1-3.1.2 contain a flaw where search-type API requests return more data than the client's OAuth scope permits, allowing unauthorized information disclosure within authorized patient boundaries.
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>= 3.1.0, < 3.1.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of fhir-works-on-aws-authz-smartLocate the package in your deployment's dependency manifest (package.json, package-lock.json, or installed node_modules). Search for 'fhir-works-on-aws-authz-smart' and note the version number.Affected if The installed version is 3.1.0, 3.1.1, or 3.1.2 (versions < 3.1.3).
-
Verify the search-type API is in use with OAuth authenticationReview your FHIR server configuration and API access patterns. Determine if clients make search-type requests (such as GET /Patient or GET /Observation?patient=123) using OAuth bearer tokens with scoped patient permissions.Affected if Search-type API endpoints are accessible using OAuth tokens with patient-specific scopes (e.g., patient/Patient.read, patient/*.read).
-
Test search results against OAuth scope boundariesUsing an OAuth client with a limited patient scope (e.g., patient/123.read), make a search request and examine the returned resources. Compare the patient references in returned resources against the permitted patient ID in the OAuth scope.Affected if The search returns resources referencing patients OTHER than the patient ID explicitly authorized in the OAuth scope token.
You are affected if fhir-works-on-aws-authz-smart version is less than 3.1.3 and your FHIR server handles search-type API requests using OAuth-scoped patient access tokens.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.3
Upgrade fhir-works-on-aws-authz-smart to version 3.1.3 or higher immediately; there is no workaround available.
3.1.3
- Upgrade fhir-works-on-aws-authz-smart to version 3.1.3 or higher using your package manager (e.g., npm install fhir-works-on-aws-authz-smart@^3.1.3)
- Verify the upgrade by checking the installed version matches the requirement
- Test your FHIR API search-type requests to confirm the authorization behavior is now correct and no longer exposes unauthorized information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39230 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39230 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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