# CVE-2022-1117: Security feature bypass in fapolicyd

> Attackers can bypass fapolicyd restrictions by exploiting incorrect runtime linker detection, allowing unauthorized application execution.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Aug 2022
- **Updated:** 2 Aug 2024
- **Also known as:** ALSA-2022:1898, AZL-10863, GHSA-8m6j-c7jr-pc5f, RHSA-2022:1898, RHSA-2022:4824, RLSA-2022:1898

## What is CVE-2022-1117?

CVE-2022-1117 is a high-severity vulnerability in fapolicyd, published on 29 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in fapolicyd. The vulnerability occurs due to an assumption on how glibc names the runtime linker, a build time regular expression may not correctly detect the runtime linker. The consequence is that the pattern detection for applications launched by the run time linker may fail to detect the pattern and allow execution.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `fapolicyd` | AlmaLinux:8 | All versions | 1.1-6.el8 |
| `fapolicyd-selinux` | AlmaLinux:8 | All versions | 1.1-6.el8 |
| `fapolicyd` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.1-6.el8 |
| `fapolicyd-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.1-6.el8 |
| `fapolicyd-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.1-6.el8 |
| `fapolicyd-selinux` | Red Hat:enterprise_linux:8::appstream | All versions | 0:1.1-6.el8 |
| `fapolicyd` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:1.0.2-6.el8_4.1 |
| `fapolicyd-debuginfo` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:1.0.2-6.el8_4.1 |
| `fapolicyd-debugsource` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:1.0.2-6.el8_4.1 |
| `fapolicyd-selinux` | Red Hat:rhel_eus:8.4::appstream | All versions | 0:1.0.2-6.el8_4.1 |
| `fapolicyd` | Rocky Linux:8 | All versions | 0:1.1-6.el8 |

Products: Fapolicyd Project Fapolicyd.

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

Apply the vendor's patch.

## Is CVE-2022-1117 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1117 is a high-severity vulnerability in fapolicyd, published on 29 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1117 in the wild and no public exploit code.

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

## Sources

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

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