LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32419: An issue in Schism Tracker v20200412 fixed in v.20200412 allows attacker to obtain sensitive information vi...

An issue in Schism Tracker v20200412 fixed in v.20200412 allows attacker to obtain sensitive information via the fmt_mtm_load_song function in fmt/mtm.c.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-32419 is a medium-severity information disclosure issue in Schism Tracker’s MTM song loader. The available sources say the flaw is in fmt_mtm_load_song in fmt/mtm.c and was addressed upstream. Business impact appears limited to confidentiality, with no cited evidence of active exploitation.

Executive priority

Treat this as a targeted medium-risk cleanup item, not an emergency. Prioritize environments that process external media files or ship Schism Tracker code to users.

Technical view

The CVE maps to CWE-787 and CVSS 3.1 score 5.3, with low confidentiality impact and no integrity or availability impact. Source metadata names Schism Tracker and the fmt_mtm_load_song function. The affected-product metadata is incomplete, so version matching should rely on upstream issue and commit evidence.

Likely exposure

Exposure is most likely where Schism Tracker or derived builds process MTM module files. The CVE record lacks normalized vendor, product, version, and CPE data, so automated scanners may miss or misclassify affected assets.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, or weaponized public exploit details. The CVSS vector indicates low-complexity, unauthenticated exposure with confidentiality-only impact, but the provided evidence is sparse.

Researcher notes

Evidence is limited to the CVE metadata, GitHub issue, and fixing commit. The CVE description says sensitive information disclosure, while the CWE is out-of-bounds write; researchers should verify root cause and affected versions from upstream history.

Mitigation direction

  • Upgrade to a Schism Tracker build containing upstream commit 1e2cc389a2a058fd13d99460c11115a6f7f7a6a4.
  • Check Schism Tracker upstream guidance for the exact fixed release or backport status.
  • Limit processing of untrusted MTM or module files until fixed builds are confirmed.
  • Prioritize systems that automatically ingest externally supplied tracker music files.

Validation and detection

  • Inventory Schism Tracker installations and any bundled or forked copies of its loader code.
  • Verify whether the deployed source or package contains the referenced upstream commit.
  • Review workflows that process MTM files from users, partners, or public sources.
  • Confirm scanners are not relying only on CPE data, because the CVE metadata is incomplete.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32419 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-32419Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.