# CVE-2022-4927: ualbertalib NEOSDiscovery _refworks.html.erb reverse tabnabbing

> Attackers can exploit reverse tabnabbing in NEOSDiscovery to redirect users to malicious sites via untrusted links.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Mar 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-j9jv-927j-jjrm

## What is CVE-2022-4927?

CVE-2022-4927 is a medium-severity vulnerability in ualbertalib NEOSDiscovery, published on 5 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in ualbertalib NEOSDiscovery 1.0.70 and classified as problematic. This issue affects some unknown processing of the file app/views/bookmarks/_refworks.html.erb. The manipulation leads to use of web link to untrusted target with window.opener access. The attack may be initiated remotely. Upgrading to version 1.0.71 is able to address this issue. The patch is named abe9f57123e0c278ae190cd7402a623d66c51375. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-222287.

Weakness: CWE-1022 (Use of Web Link to Untrusted Target with window.opener Access)

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

It affects 1 product.


Products: Ualberta Neosdiscovery.

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

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

## Is CVE-2022-4927 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4927 is a medium-severity vulnerability in ualbertalib NEOSDiscovery, published on 5 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-4927 in the wild and no public exploit code.

Affected product: ualbertalib NEOSDiscovery. 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-4927/ (Markdown: https://insights.sbomify.com/CVE-2022-4927/index.md)
```

## Sources

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

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