CVE-2013-2900: n/a vulnerability

CVE-2013-2900: The FilePath::ReferencesParent function in files/file_path.cc in Google Chrome before 29.0.1547.57 on Windo...

The FilePath::ReferencesParent function in files/file_path.cc in Google Chrome before 29.0.1547.57 on Windows does not properly handle pathname components composed entirely of . (dot) and whitespace characters, which allows remote attackers to conduct directory traversal attacks via a crafted directory name.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 15:52 UTC (UTC+00:00)

Security readout for executives and security teams

This 2013 Google Chrome Windows flaw involved unsafe handling of unusual directory names. A remote attacker could use crafted names containing dots and whitespace to cause directory traversal. Business risk is mainly legacy exposure: modern Chrome should not be affected if fully updated. Exposure is likely limited to Windows systems running Google Chrome earlier than 29.0.1547.57, plus any downstream Chromium packages covered by Debian DSA-2741. Current managed browser fleets should primarily validate absence of legacy versions. Treat this as a legacy hygiene issue unless vulnerable Chrome versions remain in production. The key decision is whether old Windows images, kiosks, or unmanaged endpoints still run pre-29 Chrome. Mitigation focus: Upgrade Google Chrome on Windows to 29.0.1547.57 or later.; Review the Chrome stable update and Debian DSA-2741 guidance for package-specific remediation.; Remove or isolate unsupported Chrome installations that cannot be upgraded..

Prepared: Jun 14, 2026, 21:50 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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2013-2900 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: Aug 21, 2013, 10: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

3Source 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
https://src.chromium.org/viewvc/chrome?revision=200603&view=revisionCVE reference · x_refsource_CONFIRM
oval:org.mitre.oval:def:18381CVE reference · vdb-entry, signature

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.