Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2025-5278

Stack-based Buffer Overflow

Published: May 27, 2025 | Modified: Jul 01, 2026
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
4.4 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:L
Ubuntu
LOW
Vulnerability-free packages from our partners
root.io logo minimus.io logo echo.ai logo
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2025-5278
CWEhttps://cwe.mitre.org/data/definitions/121.html

A flaw was found in GNU Coreutils. The sort utilitys begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.

Weakness

A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Affected Software

NameVendorStart VersionEnd Version
Red Hat Enterprise Linux 10RedHatcoreutils-0:9.5-8.el10_2*
Red Hat Enterprise Linux 9RedHatcoreutils-0:8.32-41.el9_8*
Red Hat Discovery 2RedHatdiscovery/discovery-ui-rhel9:1782756541*
Red Hat Insights proxy 1.5RedHatinsights-proxy/insights-proxy-container-rhel9:1782890503*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-gateway-opa-rhel9:1782501180*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-gateway-rhel9:1782501200*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-jaeger-query-rhel9:1782498923*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-operator-bundle:1782510941*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-query-rhel9:1782501220*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-rhel9:1782501196*
Red Hat OpenShift distributed tracing 3.10.1RedHatrhosdt/tempo-rhel9-operator:1782501195*
CoreutilsUbuntuesm-infra/xenial*
CoreutilsUbuntufocal*
CoreutilsUbuntuoracular*
CoreutilsUbuntuplucky*

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2026 Aqua Security Software Ltd.   Privacy Policy | Terms of Use