LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13351: posix/JackSocket.cpp in libjack in JACK2 1.9.1 through 1.9.12 (as distributed with alsa-plugins 1.1.7 and l...

posix/JackSocket.cpp in libjack in JACK2 1.9.1 through 1.9.12 (as distributed with alsa-plugins 1.1.7 and later) has a "double file descriptor close" issue during a failed connection attempt when jackd2 is not running. Exploitation success depends on multithreaded timing of that double close, which can result in unintended information disclosure, crashes, or file corruption due to having the wrong file associated with the file descriptor.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A JACK2 audio library bug can mishandle a failed connection when the JACK daemon is not running. Under timing-sensitive multithreaded conditions, the same file descriptor may be closed twice, potentially causing crashes, information exposure, or file corruption. Business urgency is unclear because no CVSS score, KEV listing, or active exploitation evidence is provided.

Executive priority

Track and remediate through normal vulnerability management unless local exposure involves shared, untrusted, or stability-critical audio workflows. The lack of severity scoring and exploitation evidence prevents a defensible emergency rating.

Technical view

CVE-2019-13351 affects posix/JackSocket.cpp in libjack in JACK2 1.9.1 through 1.9.12, as distributed with alsa-plugins 1.1.7 and later. During failed jackd2 connection attempts, double-closing a file descriptor can cause the descriptor to be reused for the wrong file, creating confidentiality, integrity, and availability impact possibilities.

Likely exposure

Exposure is most likely on systems with affected JACK2/libjack or alsa-plugins packages, especially audio or media applications that attempt JACK connections while jackd2 is not running. The source bundle does not identify specific operating systems or packaged fixed versions.

Exploitation context

The source states exploitation success depends on multithreaded timing during a failed connection attempt. KEV is false, and the supplied sources do not claim active exploitation. Treat exploitability as plausible but evidence-limited.

Researcher notes

The key condition is a failed jackd2 connection path in JACK2/libjack, with timing-sensitive descriptor reuse after double close. Evidence supports possible information disclosure, crash, or file corruption, but not reliable exploitation or broad product mapping.

Mitigation direction

  • Inventory JACK2/libjack and alsa-plugins versions across Linux audio and media systems.
  • Check JACK2, distribution, and application vendor guidance for fixed package availability.
  • Update affected packages through trusted distribution channels when a fixed build is identified.
  • Prioritize systems running media applications that rely on JACK under multi-user or untrusted workloads.

Validation and detection

  • Confirm whether installed JACK2/libjack versions fall within 1.9.1 through 1.9.12.
  • Identify applications linked against libjack, including media players or audio processing services.
  • Review package changelogs for CVE-2019-13351 or JackSocket double-close fixes.
  • Check logs for repeated JACK connection failures when jackd2 is not running.
  • After remediation, regression test JACK connection failure handling and application stability.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13351 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.