# CVE-2022-41950: Privilege Escalation Vulnerability by wrong chmod param

> An attacker can escalate privileges due to incorrect default file permissions in the super-xray GUI tool on Linux and macOS.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-2g28-xrw6-fq5f

## What is CVE-2022-41950?

CVE-2022-41950 is a medium-severity vulnerability in 4ra1n super-xray, published on 22 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

super-xray is the GUI alternative for vulnerability scanning tool xray. In 0.2-beta, a privilege escalation vulnerability was discovered. This caused inaccurate default xray permissions. Note: this vulnerability only affects Linux and Mac OS systems. Users should upgrade to super-xray 0.3-beta.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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

It affects 1 product.


Products: Super Xray Project Super Xray.

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

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

## Is CVE-2022-41950 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41950 exists.

## Other vulnerabilities in 4ra1n super-xray

- [CVE-2022-41958](https://insights.sbomify.com/CVE-2022-41958/): Deserialization Vulnerability by yaml config input in super-xray (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41950 is a medium-severity vulnerability in 4ra1n super-xray, published on 22 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41950 exists.

Affected product: 4ra1n super-xray. 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-41950/ (Markdown: https://insights.sbomify.com/CVE-2022-41950/index.md)
```

## Sources

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

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