CVE-2022-48554

Exp

File before 5.43 has an stack-based buffer over-read in file_copystr in funcs.c. NOTE: "File" is the name of an Open Source project.

Published: 2023-08-22 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-48554 is rated Exploit Available (53.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.66%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-48554

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-48554

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.02% 0.66% +0.63%
2 2025-11-21 0.08% 0.02% -0.06%
3 2025-11-18 — 0.08% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-48554

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.1 MEDIUM
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]

Weakness enumeration for CVE-2022-48554

OS Trackers for CVE-2022-48554

vendor priority summary link
alpine — CVE-2022-48554: 1 source package rows (file); 10 state rows across 5 repos (3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 0, open 10. https://security.alpinelinux.org/vuln/CVE-2022-48554
debian not yet assigned CVE-2022-48554 not yet assigned priority: Debian including 1 source packages (file), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2022-48554
gentoo normal CVE-2022-48554: 1 GLSA(s) (202409-06), 1 atom(s) (sys-apps/file); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-48554
redhat low — https://access.redhat.com/security/cve/CVE-2022-48554
ubuntu medium CVE-2022-48554 medium priority: Ubuntu including 1 source packages (file), 8 status rows across 8 suites (bionic, focal, jammy, lunar, mantic, trusty, upstream, xenial): not-affected 6, released 2. https://ubuntu.com/security/CVE-2022-48554

Affected software / configurations for CVE-2022-48554

Vendor Product Version Raw CPE
file_project file 5.41 cpe:2.3:a:file_project:file:5.41:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2022-48554

cvelogic Threat Intelligence