CVE-2007-0842: n/a vulnerability

CVE-2007-0842: The 64-bit versions of Microsoft Visual C++ 8.0 standard library (MSVCR80.DLL) time functions, including (1...

The 64-bit versions of Microsoft Visual C++ 8.0 standard library (MSVCR80.DLL) time functions, including (1) localtime, (2) localtime_s, (3) gmtime, (4) gmtime_s, (5) ctime, (6) ctime_s, (7) wctime, (8) wctime_s, and (9) fstat, trigger an assertion error instead of a NULL pointer or EINVAL when processing a time argument later than Jan 1, 3000, which might allow context-dependent attackers to cause a denial of service (application exit) via large time values. NOTE: it could be argued that this is a design limitation of the functions, and the vulnerability lies with any application that does not validate arguments to these functions. However, this behavior is inconsistent with documentation, which does not list assertions as a possible result of an error condition.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 12:34 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy denial-of-service issue in 64-bit Microsoft Visual C++ 8.0 runtime time-handling functions. Very large future time values can trigger an assertion instead of a documented error return, potentially causing an application to exit. Exposure is most likely in older 64-bit Windows applications built with Microsoft Visual C++ 8.0 runtime components and accepting external date, timestamp, file metadata, or serialized time values. Treat this as a low-priority legacy availability risk unless critical services still use the affected runtime and process untrusted time values. Focus on inventory and input validation rather than emergency response. Mitigation focus: Inventory legacy 64-bit applications that depend on MSVCR80.DLL.; Validate and bound external time values before calling affected runtime functions.; Check vendor or maintainer guidance for runtime updates or application-specific fixes..

Prepared: Jun 29, 2026, 07:36 UTC (UTC+00:00)

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-2007-0842 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: Feb 13, 2007, 11:00 UTC (UTC+00:00)

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

2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
visualstudio-time-dos(32454)CVE reference · vdb-entry, x_refsource_XF

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.