CVE-2022-1117

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.

Category

8.4
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.03%
Third-Party Advisory redhat.com Third-Party Advisory redhat.com Third-Party Advisory redhat.com Third-Party Advisory github.com
Affected: n/a fapolicyd
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2022-1117?
CVE-2022-1117 has been scored as a high severity vulnerability.
How to fix CVE-2022-1117?
To fix CVE-2022-1117, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-1117 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2022-1117 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-1117?
CVE-2022-1117 affects n/a fapolicyd.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.