LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37165: AbsoluteTelnet 11.12 - "license name" Denial of Service

AbsoluteTelnet 11.12 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an oversized license name. Attackers can generate a 2500-character payload and paste it into the license name field to trigger an application crash.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

AbsoluteTelnet 11.12 can be crashed by a local user entering an oversized value in the license name field. This is an availability issue for the application, not a reported data theft or remote compromise issue. Business urgency is highest where AbsoluteTelnet is used on shared, sensitive, or operationally important workstations.

Executive priority

Treat as a targeted availability risk, not an emergency remote compromise. Remediate during normal vulnerability cycles unless the software runs on critical shared systems, where earlier action is warranted.

Technical view

CVE-2020-37165 affects Celestial Software AbsoluteTelnet 11.12. The reported flaw is a local denial of service tied to improper handling of oversized license name input, mapped to CWE-120. CVSS 4.0 is 6.7 with local attack vector, low complexity, no privileges, user interaction active, and high vulnerable-system availability impact.

Likely exposure

Exposure appears limited to systems running AbsoluteTelnet 11.12 where a local user can interact with the license name field. The sources do not identify other affected versions, server-side exposure, or network-reachable exploitation.

Exploitation context

A public ExploitDB entry exists, but the source bundle does not show active exploitation and the CVE is not listed as KEV. The reported scenario requires local access and user interaction with the application interface.

Researcher notes

Evidence supports a local application crash in AbsoluteTelnet 11.12 via oversized license name handling. Public exploit information exists, but no cited source confirms in-the-wild exploitation or a vendor patch. Avoid assuming broader version impact without vendor confirmation.

Mitigation direction

  • Inventory endpoints for AbsoluteTelnet 11.12.
  • Check Celestial Software guidance for fixed versions or vendor-recommended mitigations.
  • Upgrade or remove affected installations if a supported fixed version is available.
  • Limit local interactive access on systems where the client is business-critical.
  • Prioritize remediation on shared jump hosts or operational workstations.

Validation and detection

  • Confirm installed AbsoluteTelnet versions from software inventory or endpoint management.
  • Review vendor and VulnCheck advisory details for scope updates.
  • Verify whether affected systems are shared or accessible by untrusted local users.
  • Test crash behavior only in an authorized lab environment.
  • Document compensating controls where upgrade status is unclear.
Prepared
Confidence
high
Sources
5

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-120: 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-2020-37165 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.7 (4.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 4.0 score

6.7Medium
CVSS 4.0 vector shape for CVE-2020-37165Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/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
Celestial SoftwareAbsoluteTelnet11.12Listed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.