BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2024-58251High confidence

BusyBox — Improper Neutralization of Escape, Meta, or Control Sequences

BusyBox · BusyBox

2.5LowCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.18% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs BusyBox BusyBox and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Alpine, Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

8 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Alpine v3.23v3.23 · mainbusyboxVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.37.0-r24Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainbusyboxVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.37.0-r20Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainbusyboxVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.37.0-r14Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcebusyboxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcebusyboxAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcebusyboxVendor fix publishedDebian records a fixed source-package version for this release.1:1.37.0-9Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcebusyboxVendor fix publishedDebian records a fixed source-package version for this release.1:1.37.0-9Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivebusyboxUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2024-58251 · CSAF 2.0 · revision 43 · interimSUSE Product Security TeamCVE-2024-58251
397 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • busybox as component of SLES-LTSS-TERADATA 15 SP2
  • iproute2 as component of SLES-LTSS-TERADATA 15 SP2
  • net-tools as component of SLES-LTSS-TERADATA 15 SP2
  • busybox as component of SUSE Linux Enterprise Desktop 15 SP6
  • busybox-static as component of SUSE Linux Enterprise Desktop 15 SP6
  • iproute2 as component of SUSE Linux Enterprise Desktop 15 SP6
  • iproute2-arpd as component of SUSE Linux Enterprise Desktop 15 SP6
  • iproute2-bash-completion as component of SUSE Linux Enterprise Desktop 15 SP6
  • libnetlink-devel as component of SUSE Linux Enterprise Desktop 15 SP6
  • net-tools as component of SUSE Linux Enterprise Desktop 15 SP6
  • net-tools-lang as component of SUSE Linux Enterprise Desktop 15 SP6
  • busybox as component of SUSE Linux Enterprise Desktop 15 SP7
Summary
In netstat in BusyBox through 1.37.0, local users can launch of network application with an argv[0] containing an ANSI terminal escape sequence, leading to a denial of service (terminal locked up) when netstat is used by a victim.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-12151

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Low technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In netstat in BusyBox through 1.37.0, local users can launch of network application with an argv[0] containing an ANSI terminal escape sequence, leading to a denial of service (terminal locked up) when netstat is used by a victim.

What

In netstat in BusyBox through 1.37.0, local users can launch of network application with an argv[0] containing an ANSI terminal escape sequence, leading to a denial of service (terminal locked up) when netstat is used by a victim.

Why

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may disrupt the affected service.

What

In netstat in BusyBox through 1.37.0, local users can launch of network application with an argv[0] containing an ANSI terminal escape sequence, leading to a denial of service (terminal locked up) when netstat is used by a victim.

Why

The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.

How

An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Neutralization of Escape, Meta, or Control Sequences → disrupt the affected service
Attack surface
Local
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-150 ↗

CWE-150: Improper Neutralization of Escape, Meta, or Control Sequences. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:L

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ALowAvailability impact: A successful attack can cause a limited loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
UnauthenticatedDenial of serviceCWE-150
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2025-0879BusyBox: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in BusyBox ausnutzen, um einen Denial of Service Angriff durchzuführen und um Dateien zu manipulieren.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0627Multiples vulnérabilités dans les produits Splunk

ecord?id=CVE-2024-45337 Référence CVE CVE-2024-45339 https://www.cve.org/CVERecord?id=CVE-2024-45339 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-47561 https://www.cve.org/CVERecord?id=CVE-2024-47561 Référence CVE CVE-2024-52304 https://www.cve.org/CVERecord?id=CVE-2024-52304 Référence CVE CVE-2024-5321 https://www.cve.org/CVERecord?id=CVE-2024-5321 Référence CVE CVE-2024-53899 https://www.cve.org/CVERecord?id=CVE-2024-53899 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-7592 https://www.cve.org/CVERecord?id=CVE-2024-7592 Référence CVE CVE-2024-8775 https://www.cve.org/CVERecord?id=CVE-2024-8775 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0938 https://www.cve.org/CVERecord?id=CVE-2025-0938 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CVE-2025-11143 Référence CVE CVE-2025-11187 https://www.cve.org/CVERecord?id=CVE-2025-111

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2024-58098 https://www.cve.org/CVERecord?id=CVE-2024-58098 Référence CVE CVE-2024-58100 https://www.cve.org/CVERecord?id=CVE-2024-58100 Référence CVE CVE-2024-58237 https://www.cve.org/CVERecord?id=CVE-2024-58237 Référence CVE CVE-2024-58238 https://www.cve.org/CVERecord?id=CVE-2024-58238 Référence CVE CVE-2024-58241 https://www.cve.org/CVERecord?id=CVE-2024-58241 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-6519 https://www.cve.org/CVERecord?id=CVE-2024-6519 Référence CVE CVE-2024-7883 https://www.cve.org/CVERecord?id=CVE-2024-7883 Référence CVE CVE-2024-8354 https://www.cve.org/CVERecord?id=CVE-2024-8354 Référence CVE CVE-2024-8612 https://www.cve.org/CVERecord?id=CVE-2024-8612 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2025-0012 https://www.cve.org/CVERecord?id=CVE-2025-0012 R

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0316Multiples vulnérabilités dans les produits VMware

d?id=CVE-2024-58094 Référence CVE CVE-2024-58095 https://www.cve.org/CVERecord?id=CVE-2024-58095 Référence CVE CVE-2024-58096 https://www.cve.org/CVERecord?id=CVE-2024-58096 Référence CVE CVE-2024-58097 https://www.cve.org/CVERecord?id=CVE-2024-58097 Référence CVE CVE-2024-58098 https://www.cve.org/CVERecord?id=CVE-2024-58098 Référence CVE CVE-2024-58100 https://www.cve.org/CVERecord?id=CVE-2024-58100 Référence CVE CVE-2024-58237 https://www.cve.org/CVERecord?id=CVE-2024-58237 Référence CVE CVE-2024-58238 https://www.cve.org/CVERecord?id=CVE-2024-58238 Référence CVE CVE-2024-58241 https://www.cve.org/CVERecord?id=CVE-2024-58241 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-6519 https://www.cve.org/CVERecord?id=CVE-2024-6519 Référence CVE CVE-2024-7883 https://www.cve.org/CVERecord?id=CVE-2024-7883 Référence CVE CVE-2024-8354 https://www.cve.org/CVERecord?id=CVE-2024-8354 Référence CVE CVE-2024-8612 https://www.cve.org/CVERecord?id=CVE-2024-8612 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2025-0012 https://www.cve.org/CVERecord?id=CVE-2025-0012 R

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0281Multiples vulnérabilités dans les produits Splunk

ord?id=CVE-2024-38286 Référence CVE CVE-2024-47081 https://www.cve.org/CVERecord?id=CVE-2024-47081 Référence CVE CVE-2024-50379 https://www.cve.org/CVERecord?id=CVE-2024-50379 Référence CVE CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 Référence CVE CVE-2024-52316 https://www.cve.org/CVERecord?id=CVE-2024-52316 Référence CVE CVE-2024-54677 https://www.cve.org/CVERecord?id=CVE-2024-54677 Référence CVE CVE-2024-56337 https://www.cve.org/CVERecord?id=CVE-2024-56337 Référence CVE CVE-2024-5642 https://www.cve.org/CVERecord?id=CVE-2024-5642 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-7246 https://www.cve.org/CVERecord?id=CVE-2024-7246 Référence CVE CVE-2024-8372 https://www.cve.org/CVERecord?id=CVE-2024-8372 Référence CVE CVE-2024-8373 https://www.cve.org/CVERecord?id=CVE-2024-8373 Référence CVE CVE-2025-0518 https://www.cve.org/CVERecord?id=CVE-2025-0518 Référence CVE CVE-2025-0716 https://www.cve.org/CVERecord?id=CVE-2025-0716 Référence CVE CVE-2025-0913 https://www.cve.org/CVERecord?id=CVE-2025-0913 Référence CVE CVE-2025-10148 https://www.cve.org/CVERecord?id=CVE-2025-10148 Référence CVE CVE-2025-10256 https://www.cve.org/CVERecord?id=CVE-2025-102

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2024-55549 Référence CVE CVE-2024-56171 https://www.cve.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-56406 https://www.cve.org/CVERecord?id=CVE-2024-56406 Référence CVE CVE-2024-5642 https://www.cve.org/CVERecord?id=CVE-2024-5642 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-57360 https://www.cve.org/CVERecord?id=CVE-2024-57360 Référence CVE CVE-2024-57970 https://www.cve.org/CVERecord?id=CVE-2024-57970 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6232 https://www.cve.org/CVERecord?id=CVE-2024-6232 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-7006 https://www.cve.org/CVERecord?id=CVE-2024-7006 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8088 https://www.cve.org/CVERecord?id=CVE-2024-8088 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 R

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2024-47554 Référence CVE CVE-2024-47561 https://www.cve.org/CVERecord?id=CVE-2024-47561 Référence CVE CVE-2024-51744 https://www.cve.org/CVERecord?id=CVE-2024-51744 Référence CVE CVE-2024-53114 https://www.cve.org/CVERecord?id=CVE-2024-53114 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-5642 https://www.cve.org/CVERecord?id=CVE-2024-5642 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56538 https://www.cve.org/CVERecord?id=CVE-2024-56538 Référence CVE CVE-2024-58011 https://www.cve.org/CVERecord?id=CVE-2024-58011 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 Référence CVE CVE-2024-7264 https://www.cve.org/CVERecord?id=CVE-2024-7264 Référence CVE CVE-2024-8096 https://www.cve.org/CVERecord?id=CVE-2024-8096 Référence CVE CVE-2024-9143 https://www.cve.org/CVERecord?id=CVE-2024-9143 Référence CVE CVE-2024-9681 https://www.cve.org/CVERecord?id=CVE-2024-9681 Référence CVE CVE-2025-0167 https://www.cve.org/CVERecord?id=CVE-2025-0167 Référence CVE CVE-2025-0725 https://www.cve.org/CVERecord?id=CVE-2025-0725 R

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2024-54458 Référence CVE CVE-2024-5535 https://www.cve.org/CVERecord?id=CVE-2024-5535 Référence CVE CVE-2024-55549 https://www.cve.org/CVERecord?id=CVE-2024-55549 Référence CVE CVE-2024-56171 https://www.cve.org/CVERecord?id=CVE-2024-56171 Référence CVE CVE-2024-56406 https://www.cve.org/CVERecord?id=CVE-2024-56406 Référence CVE CVE-2024-56433 https://www.cve.org/CVERecord?id=CVE-2024-56433 Référence CVE CVE-2024-56664 https://www.cve.org/CVERecord?id=CVE-2024-56664 Référence CVE CVE-2024-56751 https://www.cve.org/CVERecord?id=CVE-2024-56751 Référence CVE CVE-2024-58093 https://www.cve.org/CVERecord?id=CVE-2024-58093 Référence CVE CVE-2024-58251 https://www.cve.org/CVERecord?id=CVE-2024-58251 Référence CVE CVE-2024-6119 https://www.cve.org/CVERecord?id=CVE-2024-6119 Référence CVE CVE-2024-6174 https://www.cve.org/CVERecord?id=CVE-2024-6174 Référence CVE CVE-2024-6232 https://www.cve.org/CVERecord?id=CVE-2024-6232 Référence CVE CVE-2024-6345 https://www.cve.org/CVERecord?id=CVE-2024-6345 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2024-6923 https://www.cve.org/CVERecord?id=CVE-2024-6923 Référence CVE CVE-2024-7012 https://www.cve.org/CVERecord?id=CVE-2024-7012 Référence CVE CVE-2024-7254 https://www.cve.org/CVERecord?id=CVE-2024-7254 R

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 23 Apr 2025 · Last source change 23 Apr 2025, 23:02 UTC · CWE-150 · Improper Neutralization of Escape, Meta, or Control Sequences

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-12151
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    SUSE Product Security Team ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Remediation guidance recorded
ENISA EUVD · EUVD-2025-12151↗SUSE Product Security Team security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-58251 · cve.blacktree.nl