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

An Improper Link Resolution Before File Access ("Link Following") and Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal")

Unknown · Unknown

7.5HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, 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 2.25% 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 Unknown Unknown 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 30 daysRemediation target: Within 180 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.

Distribution package intelligence

Release-specific package status

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

5 package states
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
Debian trixietrixie · sourcenode-tar-fsVendor fix publishedDebian records a fixed source-package version for this release.3.0.8+~cs2.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcenode-tar-fsVendor fix publishedDebian records a fixed source-package version for this release.2.1.3-0+deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcenode-tar-fsVendor fix publishedDebian records a fixed source-package version for this release.3.0.8+~cs2.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcenode-tar-fsVendor fix publishedDebian records a fixed source-package version for this release.3.0.8+~cs2.0.4-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsnode-tar-fsVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.2.1.1-6ubuntu0.24.04.1~esm1Canonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
npmtar-fs< 1.16.41.16.4GitHub advisory ↗github reviewed aggregator · 3 Nov 2025
npmtar-fs>= 2.0.0, < 2.1.22.1.2GitHub advisory ↗github reviewed aggregator · 3 Nov 2025
npmtar-fs>= 3.0.0, < 3.0.73.0.7GitHub advisory ↗github reviewed aggregator · 3 Nov 2025
npmtar-fsSEMVER: introduced 0; fixed 1.16.41.16.4OSV record ↗aggregator derived · 10 Sep 2026
npmtar-fsSEMVER: introduced 2.0.0; fixed 2.1.22.1.2OSV record ↗aggregator derived · 10 Sep 2026
npmtar-fsSEMVER: introduced 3.0.0; fixed 3.0.73.0.7OSV record ↗aggregator derived · 10 Sep 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-12905 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitytar-fs: link following and path traversal via maliciously crafted tar file
56 known affected

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

  • ceph-base as a component of Red Hat Ceph Storage 8
  • ceph-common as a component of Red Hat Ceph Storage 8
  • ceph-fuse as a component of Red Hat Ceph Storage 8
  • ceph-immutable-object-cache as a component of Red Hat Ceph Storage 8
  • ceph-mib as a component of Red Hat Ceph Storage 8
  • ceph-resource-agents as a component of Red Hat Ceph Storage 8
  • ceph-selinux as a component of Red Hat Ceph Storage 8
  • ceph.src as a component of Red Hat Ceph Storage 8
  • cephadm as a component of Red Hat Ceph Storage 8
  • cephfs-top as a component of Red Hat Ceph Storage 8
  • libcephfs-devel as a component of Red Hat Ceph Storage 8
  • libcephfs-proxy2 as a component of Red Hat Ceph Storage 8
Summary
A flaw was found in the tar-fs package for Node.js. In affected versions, unauthorized file writes or overwrites outside the intended extraction directory can occur when extracting a maliciously crafted tar file. The issue is associated with index.js in the tar-fs package.
Remediation
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
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-54315

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 actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

An Improper Link Resolution Before File Access ("Link Following") and Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal"). This vulnerability occurs when extracting a maliciously crafted tar file, which can result in unauthorized file writes or overwrites outside the intended extraction directory. The issue is associated with index.js in the tar-fs package. This issue affects tar-fs: from 0.0.0 before 1.16.4, from 2.0.0 before 2.1.2, from 3.0.0 before 3.0.8.

What

An Improper Link Resolution Before File Access ("Link Following") and Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal"). This vulnerability occurs when extracting a maliciously crafted tar file, which can result in unauthorized file writes or overwrites outside the intended extraction directory. The issue is associated with index.js in the tar-fs package. This issue affects tar-fs: from 0.0.0 before 1.16.4, from 2.0.0 before 2.1.2, from 3.0.0 before 3.0.8.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

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

An Improper Link Resolution Before File Access ("Link Following") and Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal"). This vulnerability occurs when extracting a maliciously crafted tar file, which can result in unauthorized file writes or overwrites outside the intended extraction directory. The issue is associated with index.js in the tar-fs package. This issue affects tar-fs: from 0.0.0 before 1.16.4, from 2.0.0 before 2.1.2, from 3.0.0 before 3.0.8.

Why

The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

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 → Improper Link Resolution Before File Access ('Link 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-59 ↗

CWE-59: Improper Link Resolution Before File Access ('Link Following'). The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.

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:N/I:H/A:N

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.CNoneConfidentiality impact: No direct loss is represented by this metric.IHighIntegrity impact: A successful attack can cause a major loss.ANoneAvailability impact: No direct loss is represented by this metric.
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-59
A

Official authority intelligence

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

Cyber Security Agency of Singapore · English · CSA-SB-20250402Security Bulletin 02 Apr 2025 [1.46 MB]

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 02 Apr 2025 [1.46 MB], published on 2 April 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

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

cord?id=CVE-2020-8908 Référence CVE CVE-2021-22569 https://www.cve.org/CVERecord?id=CVE-2021-22569 Référence CVE CVE-2021-22570 https://www.cve.org/CVERecord?id=CVE-2021-22570 Référence CVE CVE-2021-23337 https://www.cve.org/CVERecord?id=CVE-2021-23337 Référence CVE CVE-2021-47154 https://www.cve.org/CVERecord?id=CVE-2021-47154 Référence CVE CVE-2022-22968 https://www.cve.org/CVERecord?id=CVE-2022-22968 Référence CVE CVE-2022-39135 https://www.cve.org/CVERecord?id=CVE-2022-39135 Référence CVE CVE-2023-22899 https://www.cve.org/CVERecord?id=CVE-2023-22899 Référence CVE CVE-2023-5752 https://www.cve.org/CVERecord?id=CVE-2023-5752 Référence CVE CVE-2024-12905 https://www.cve.org/CVERecord?id=CVE-2024-12905 Référence CVE CVE-2024-23953 https://www.cve.org/CVERecord?id=CVE-2024-23953 Référence CVE CVE-2024-29869 https://www.cve.org/CVERecord?id=CVE-2024-29869 Référence CVE CVE-2024-38820 https://www.cve.org/CVERecord?id=CVE-2024-38820 Référence CVE CVE-2024-38827 https://www.cve.org/CVERecord?id=CVE-2024-38827 Référence CVE CVE-2024-45337 https://www.cve.org/CVERecord?id=CVE-2024-45337 Référence CVE CVE-2024-52046 https://www.cve.org/CVERecord?id=CVE-2024-52046 Référence CVE CVE-2024-6763 https://www.cve.org/CVERecord?id=CVE-2024-6763 Référence CVE CVE-2025-11143 https://www.cve.org/CVERecord?id=CV

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

De multiples vulnérabilités ont été découvertes dans les produits NetApp. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à la confidentialité des données et une atteinte à l'intégrité des données.

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

ord?id=CVE-2023-42503 Référence CVE CVE-2023-43804 https://www.cve.org/CVERecord?id=CVE-2023-43804 Référence CVE CVE-2023-45133 https://www.cve.org/CVERecord?id=CVE-2023-45133 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2023-5676 https://www.cve.org/CVERecord?id=CVE-2023-5676 Référence CVE CVE-2024-10917 https://www.cve.org/CVERecord?id=CVE-2024-10917 Référence CVE CVE-2024-12085 https://www.cve.org/CVERecord?id=CVE-2024-12085 Référence CVE CVE-2024-12797 https://www.cve.org/CVERecord?id=CVE-2024-12797 Référence CVE CVE-2024-12905 https://www.cve.org/CVERecord?id=CVE-2024-12905 Référence CVE CVE-2024-20918 https://www.cve.org/CVERecord?id=CVE-2024-20918 Référence CVE CVE-2024-20919 https://www.cve.org/CVERecord?id=CVE-2024-20919 Référence CVE CVE-2024-20921 https://www.cve.org/CVERecord?id=CVE-2024-20921 Référence CVE CVE-2024-20926 https://www.cve.org/CVERecord?id=CVE-2024-20926 Référence CVE CVE-2024-20945 https://www.cve.org/CVERecord?id=CVE-2024-20945 Référence CVE CVE-2024-20952 https://www.cve.org/CVERecord?id=CVE-2024-20952 Référence CVE CVE-2024-21011 https://www.cve.org/CVERecord?id=CVE-2024-21011 Référence CVE CVE-2024-21068 https://www.cve.org/CVERecord?id=

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

curité VMware DSA-2025-25 du 18 décembre 2025 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36626 Bulletin de sécurité VMware DSA-2025-25 du 18 décembre 2025 https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/36627 Référence CVE CVE-2020-7792 https://www.cve.org/CVERecord?id=CVE-2020-7792 Référence CVE CVE-2022-29526 https://www.cve.org/CVERecord?id=CVE-2022-29526 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-48795 https://www.cve.org/CVERecord?id=CVE-2023-48795 Référence CVE CVE-2024-12905 https://www.cve.org/CVERecord?id=CVE-2024-12905 Référence CVE CVE-2024-21538 https://www.cve.org/CVERecord?id=CVE-2024-21538 Référence CVE CVE-2024-25126 https://www.cve.org/CVERecord?id=CVE-2024-25126 Référence CVE CVE-2024-25621 https://www.cve.org/CVERecord?id=CVE-2024-25621 Référence CVE CVE-2024-26141 https://www.cve.org/CVERecord?id=CVE-2024-26141 Référence CVE CVE-2024-26146 https://www.cve.org/CVERecord?id=CVE-2024-26146 Référence CVE CVE-2024-3044 https://www.cve.org/CVERecord?id=CVE-2024-3044 Référence CVE CVE-2024-34155 https://www.cve.org/CVERecord?id=CVE-2024-34155 Référence CVE CVE-2024-34158 https://www.cve.org/CVERecord?id=CV

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

De multiples vulnérabilités ont été découvertes dans les produits Atlassian. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

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

té IBM 7253227 du 01 décembre 2025 https://www.ibm.com/support/pages/node/7253227 Bulletin de sécurité IBM 7253232 du 01 décembre 2025 https://www.ibm.com/support/pages/node/7253232 Bulletin de sécurité IBM 7253254 du 01 décembre 2025 https://www.ibm.com/support/pages/node/7253254 Bulletin de sécurité IBM 7253281 du 01 décembre 2025 https://www.ibm.com/support/pages/node/7253281 Bulletin de sécurité IBM 7253432 du 02 décembre 2025 https://www.ibm.com/support/pages/node/7253432 Référence CVE CVE-2019-20149 https://www.cve.org/CVERecord?id=CVE-2019-20149 Référence CVE CVE-2023-39017 https://www.cve.org/CVERecord?id=CVE-2023-39017 Référence CVE CVE-2024-12905 https://www.cve.org/CVERecord?id=CVE-2024-12905 Référence CVE CVE-2024-45296 https://www.cve.org/CVERecord?id=CVE-2024-45296 Référence CVE CVE-2024-47764 https://www.cve.org/CVERecord?id=CVE-2024-47764 Référence CVE CVE-2024-52798 https://www.cve.org/CVERecord?id=CVE-2024-52798 Référence CVE CVE-2024-55565 https://www.cve.org/CVERecord?id=CVE-2024-55565 Référence CVE CVE-2025-12758 https://www.cve.org/CVERecord?id=CVE-2025-12758 Référence CVE CVE-2025-27152 https://www.cve.org/CVERecord?id=CVE-2025-27152 Référence CVE CVE-2025-27789 https://www.cve.org/CVERecord?id=CVE-2025-27789 Référence CVE CVE-2025-30749 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-44981 Référence CVE CVE-2023-45178 https://www.cve.org/CVERecord?id=CVE-2023-45178 Référence CVE CVE-2023-45288 https://www.cve.org/CVERecord?id=CVE-2023-45288 Référence CVE CVE-2023-45853 https://www.cve.org/CVERecord?id=CVE-2023-45853 Référence CVE CVE-2023-50298 https://www.cve.org/CVERecord?id=CVE-2023-50298 Référence CVE CVE-2023-52428 https://www.cve.org/CVERecord?id=CVE-2023-52428 Référence CVE CVE-2023-52922 https://www.cve.org/CVERecord?id=CVE-2023-52922 Référence CVE CVE-2024-10963 https://www.cve.org/CVERecord?id=CVE-2024-10963 Référence CVE CVE-2024-12797 https://www.cve.org/CVERecord?id=CVE-2024-12797 Référence CVE CVE-2024-12905 https://www.cve.org/CVERecord?id=CVE-2024-12905 Référence CVE CVE-2024-1737 https://www.cve.org/CVERecord?id=CVE-2024-1737 Référence CVE CVE-2024-1975 https://www.cve.org/CVERecord?id=CVE-2024-1975 Référence CVE CVE-2024-21634 https://www.cve.org/CVERecord?id=CVE-2024-21634 Référence CVE CVE-2024-22201 https://www.cve.org/CVERecord?id=CVE-2024-22201 Référence CVE CVE-2024-23454 https://www.cve.org/CVERecord?id=CVE-2024-23454 Référence CVE CVE-2024-25062 https://www.cve.org/CVERecord?id=CVE-2024-25062 Référence CVE CVE-2024-25638 https://www.cve.org/CVERecord?id=CVE-2024-25638 Référence CVE CVE-2024-25710 https://www.cve.org/CVERecord?id=CVE-

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.
Patch available
Affected
Fixed
Action
Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
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 27 Mar 2025 · Last source change 3 Nov 2025, 19:29 UTC · CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVE recordCVE.org · 5.2
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-2024-54315
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    0.0.0 < 1.16.4; 2.0.0 < 2.1.2; 3.0.0 < 3.0.8 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    0.0.0 < 1.16.4; 2.0.0 < 2.1.2; 3.0.0 < 3.0.8 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2024-54315↗Red Hat Product Security 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-12905 · cve.blacktree.nl