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

readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file

dest-unreach · socat

9.8CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 1 structured product or package state 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 severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.80% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs dest-unreach socat 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: Within 3 daysRemediation target: Within 90 days

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 1 structured product or package state 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 1 affected package state 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 · mainsocatVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainsocatVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainsocatVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcesocatVendor fix publishedDebian records a fixed source-package version for this release.1.8.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcesocatAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcesocatVendor fix publishedDebian records a fixed source-package version for this release.1.8.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcesocatVendor fix publishedDebian records a fixed source-package version for this release.1.8.0.2-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivesocatVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.8.0.0-4ubuntu0.1Canonical 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-54661 · CSAF 2.0 · revision 48 · interimSUSE Product Security TeamCVE-2024-54661
64 known affected

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

  • socat as component of SUSE Enterprise Storage 7.1
  • socat as component of SUSE Linux Enterprise High Performance Computing 12 SP2
  • socat as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • socat as component of SUSE Linux Enterprise High Performance Computing 12 SP5
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP2
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP3
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • socat as component of SUSE Linux Enterprise High Performance Computing 15 SP4
Summary
readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file.
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-2024-52644

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

Critical technical impact with a remotely reachable, unauthenticated path; no CISA KEV confirmation is currently recorded. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file.

What

readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file.

Why

The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

readline.sh in socat before1.8.0.2 relies on the /tmp/$USER/stderr2 file.

Why

The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

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
a network path → UNIX Symbolic Link (Symlink) Following → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
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-61 ↗

CWE-61: UNIX Symbolic Link (Symlink) Following. The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

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

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-61
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1905IBM QRadar SIEM Komponente: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM Komponenten ausnutzen, um Daten zu manipulieren, um einen Denial of Service Angriff durchzuführen, um beliebigen Programmcode auszuführen, um Sicherheitsvorkehrungen zu umgehen, und um Informationen offenzulegen.

Official advisory ↗
BSI · German · WID-SEC-2025-1466Red Hat Enterprise Linux (socat): Schwachstelle ermöglicht Manipulation von Dateien

Ein lokaler Angreifer kann eine Schwachstelle im "socat" Paket von Red Hat Enterprise Linux ausnutzen, um Dateien zu manipulieren.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241211Security Bulletin 11 Dec 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Dec 2024, published on 11 December 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

d?id=CVE-2024-34397 Référence CVE CVE-2024-43420 https://www.cve.org/CVERecord?id=CVE-2024-43420 Référence CVE CVE-2024-45332 https://www.cve.org/CVERecord?id=CVE-2024-45332 Référence CVE CVE-2024-47535 https://www.cve.org/CVERecord?id=CVE-2024-47535 Référence CVE CVE-2024-50154 https://www.cve.org/CVERecord?id=CVE-2024-50154 Référence CVE CVE-2024-50349 https://www.cve.org/CVERecord?id=CVE-2024-50349 Référence CVE CVE-2024-52006 https://www.cve.org/CVERecord?id=CVE-2024-52006 Référence CVE CVE-2024-52533 https://www.cve.org/CVERecord?id=CVE-2024-52533 Référence CVE CVE-2024-53920 https://www.cve.org/CVERecord?id=CVE-2024-53920 Référence CVE CVE-2024-54661 https://www.cve.org/CVERecord?id=CVE-2024-54661 Référence CVE CVE-2024-57980 https://www.cve.org/CVERecord?id=CVE-2024-57980 Référence CVE CVE-2024-58002 https://www.cve.org/CVERecord?id=CVE-2024-58002 Référence CVE CVE-2024-6531 https://www.cve.org/CVERecord?id=CVE-2024-6531 Référence CVE CVE-2025-1470 https://www.cve.org/CVERecord?id=CVE-2025-1470 Référence CVE CVE-2025-1471 https://www.cve.org/CVERecord?id=CVE-2025-1471 Référence CVE CVE-2025-1494 https://www.cve.org/CVERecord?id=CVE-2025-1494 Référence CVE CVE-2025-1994 https://www.cve.org/CVERecord?id=CVE-2025-1994 Référence CVE CVE-2025-20012 https://www.cve.org/CVERecord?id=CVE-2025-2

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. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 4 Dec 2024 · Last source change 9 Jan 2025, 16:30 UTC · CWE-61 · UNIX Symbolic Link (Symlink) Following

CVE recordCVE.org · 5.1
CVSS sourceCISA ADP
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-2024-52644
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-2024-52644↗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-54661 · cve.blacktree.nl