LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19787: ATasm 1.06 has a stack-based buffer overflow in the get_signed_expression() function in setparse.c via a cr...

ATasm 1.06 has a stack-based buffer overflow in the get_signed_expression() function in setparse.c via a crafted .m65 file.

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

Security readout for executives and security teams

Plain-English summary

CVE-2019-19787 affects ATasm 1.06, an assembler tool. A specially crafted .m65 input file can trigger a stack-based buffer overflow. The public data does not provide CVSS scoring or confirmed real-world exploitation, so urgency depends on whether the tool processes files from untrusted sources.

Executive priority

Treat this as a targeted tooling risk, not an internet-facing emergency. Prioritize remediation if ATasm is used in build environments, accepts third-party files, or runs in shared automation where a parser crash or memory-corruption event could disrupt operations.

Technical view

The reported flaw is a stack-based buffer overflow in ATasm 1.06 within get_signed_expression() in setparse.c, reachable through parsing a crafted .m65 file. Public sources identify Fedora advisories, but the provided bundle does not include a CVSS vector, CWE mapping, or detailed fixed-version information.

Likely exposure

Exposure is likely limited to systems where ATasm 1.06 is installed and used manually, in build pipelines, or in automated processing of .m65 files from external or untrusted contributors.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The realistic risk is malicious or malformed source files causing a crash or possibly memory-corruption impact when opened or built with vulnerable ATasm.

Researcher notes

Evidence is sparse: the bundle names the vulnerable function, version, and file type, plus Fedora advisories. It does not provide exploit maturity, a CVSS vector, confirmed fix details, or broader affected-version ranges. Do not extrapolate beyond ATasm 1.06 without vendor confirmation.

Mitigation direction

  • Inventory ATasm installations and identify any version 1.06 usage.
  • Avoid processing untrusted .m65 files with affected ATasm builds.
  • Review the listed Fedora advisories for applicable package updates.
  • Check upstream or distribution maintainer guidance for fixed versions.
  • Restrict ATasm use in automated pipelines handling external submissions.

Validation and detection

  • Confirm whether ATasm is installed on developer workstations or build systems.
  • Check package metadata to determine the installed ATasm version.
  • Review CI workflows for automated handling of .m65 files.
  • Verify whether Fedora advisory updates are applied where relevant.
  • Look for historical crashes during ATasm parsing or builds.
Prepared
Confidence
medium
Sources
6

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-19787 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
5Source 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.