LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25570: RealTerm Serial Terminal 2.0.0.70 Denial of Service via Port Field

RealTerm Serial Terminal 2.0.0.70 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an excessively long string in the Port field. Attackers can paste a buffer of 1000 characters into the Port input field and click the open button to trigger a crash.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-25570 is a local denial-of-service issue in RealTerm Serial Terminal 2.0.0.70. A person with access to the application can crash it through the Port field. Business impact is limited to application availability, but it may disrupt serial-device operations where RealTerm is used for testing, support, or operations.

Executive priority

Treat as a targeted operational reliability issue, not an enterprise-wide remote compromise risk. Prioritize environments where RealTerm supports production, lab, or customer-facing serial-device workflows.

Technical view

RealTerm Serial Terminal 2.0.0.70 mishandles an overly long Port field value, causing an application crash. The CVSS v4 score is 6.8 with local attack vector, low complexity, no privileges, and user interaction present. The reported impact is high availability loss for the vulnerable application, with no confidentiality or integrity impact stated.

Likely exposure

Exposure is likely limited to endpoints or workstations where RealTerm Serial Terminal 2.0.0.70 is installed and locally used. Systems not running this version are not identified as affected in the provided sources.

Exploitation context

A public Exploit-DB reference exists, but the provided sources do not show active exploitation or CISA KEV listing. Exploitation requires local interaction with the application, reducing broad remote risk.

Researcher notes

The evidence describes a local application crash via malformed Port field input. Sources do not name a patched version or vendor mitigation. Avoid assuming broader memory corruption impact beyond denial of service unless additional analysis confirms it.

Mitigation direction

  • Inventory RealTerm installations and identify version 2.0.0.70.
  • Check RealTerm official pages and SourceForge files for vendor guidance or newer releases.
  • Avoid using the affected version for critical serial-device operations where crashes cause disruption.
  • Limit local access to systems where vulnerable RealTerm installations are required.
  • Do not test crash behavior on production workstations.

Validation and detection

  • Confirm installed RealTerm version on engineering, lab, and support workstations.
  • Review helpdesk or endpoint logs for RealTerm crash reports.
  • Map business processes that depend on RealTerm availability.
  • Verify whether a newer vendor-provided release is approved and deployable.
  • Document compensating controls if version 2.0.0.70 must remain in use.
Prepared
Confidence
medium
Sources
6

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-1260: 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-2019-25570 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
6.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA: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
5Source 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
6.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.8Medium
CVSS 4.0 vector shape for CVE-2019-25570Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
RealtermRealTerm: Serial Terminal2.0.0.70Listed
Weakness

CWE details

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

CWE-1260 · source CWE mapping

Improper Handling of Overlap Between Protected Memory Ranges

Improper Handling of Overlap Between Protected Memory Ranges represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.