LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37109: aSc TimeTables 2020.11.4 - Denial of Service

aSc TimeTables 2020.11.4 contains a denial of service vulnerability that allows attackers to crash the application by overwriting the Subject title field with a large buffer. Attackers can generate a 1000-character buffer and paste it into the Subject title to trigger an application crash and potential instability.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-37109 is a denial-of-service flaw in aSc TimeTables 2020.11.4. A malformed oversized entry in the Subject title field can crash the application. The main business risk is disruption to timetable creation or administration, not data theft. Public exploit information exists, but the provided sources do not show active exploitation.

Executive priority

Treat as a targeted availability risk for teams relying on aSc TimeTables. Prioritize if the affected version supports active school or workforce scheduling operations. This is less urgent than remote code execution, but downtime during planning cycles could be disruptive.

Technical view

The record describes a CWE-120 buffer issue affecting aSc TimeTables 2020.11.4. The CVSS 3.1 score is 7.5, with availability impact only. The description says application crash through an oversized Subject title value. Sources conflict somewhat: the vector lists network/no interaction, while the described trigger appears application-input based.

Likely exposure

Exposure is likely limited to organizations running aSc TimeTables 2020.11.4. Impact is application availability and potential instability. The sources do not identify other affected versions, server components, or platforms.

Exploitation context

ExploitDB lists a public exploit reference, so proof-of-concept information is publicly available. CISA KEV is not indicated in the provided bundle, and no cited source confirms active exploitation. The described impact is a crash, not code execution or data compromise.

Researcher notes

The affected version is specifically 2020.11.4. The CVSS vector suggests network reachability and no user interaction, but the vulnerability description centers on oversized input in a Subject title field. Do not assume broader reachability without vendor or advisory confirmation.

Mitigation direction

  • Identify any installations of aSc TimeTables 2020.11.4.
  • Check the vendor site or support channel for updated versions or guidance.
  • Prioritize upgrading or replacing affected installations if vendor guidance confirms a fix.
  • Limit use of affected versions for business-critical scheduling workflows.
  • Back up timetable data before remediation or version changes.

Validation and detection

  • Confirm installed aSc TimeTables version from application inventory or endpoint records.
  • Review help/about screens or software management data for version 2020.11.4.
  • Check whether scheduling teams still depend on the affected application.
  • Verify vendor guidance before performing any crash reproduction testing.
  • Document remediation status and residual operational dependency.
Prepared
Confidence
medium
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-37109 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2020-37109Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
asc Applied Software ConsultantsaSc TimeTables2020.11.4Listed
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.