CVE-2022-1117

Policy bypass via misidentified runtime linker

Published Aug 29, 2022 · Updated Aug 2, 2024

Improper runtime-linker detection in fapolicyd before 1.1.2 allows local users to execute applications that policy should block. The dyn_linker.m4 build macro resolves only /usr/lib64/ld-2.*.so, so changed glibc linker names can leave SYSTEM_LD_SO pointing at the wrong path and disable the ld_so matcher. A local user must invoke an application through the unrecognized runtime linker; the result is execution of code that the active allowlisting policy otherwise denies.

CVSS severity8.4
High
EPSS probability0.33%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper runtime-linker detection in fapolicyd before 1.1.2 allows local users to execute applications that policy should block. The dyn_linker.m4 build macro resolves only /usr/lib64/ld-2.*.so, so changed glibc linker names can leave SYSTEM_LD_SO pointing at the wrong path and disable the ld_so matcher. A local user must invoke an application through the unrecognized runtime linker; the result is execution of code that the active allowlisting policy otherwise denies.

The record

CVE
CVE-2022-1117
Published
Aug 29, 2022
Updated
Aug 2, 2024
Vendor
Fapolicyd Project
Product
fapolicyd
Classifications
CWE-552, T1218
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 29, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Fixed in v1.1.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Fapolicyd Project · fapolicydversion=Fixed in v1.1.2

Published CVSS scores

8.4NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-552Files or Directories Accessible to External Parties
T1218System Binary Proxy Execution

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo