LiveActive security incident?Get immediate response
CVE Record

CVE-2005-4474: Buffer overflow in the "Add to archive" command in WinRAR 3.51 allows user-assisted attackers to cause a de...

Buffer overflow in the "Add to archive" command in WinRAR 3.51 allows user-assisted attackers to cause a denial of service (crash) and possibly execute arbitrary code by tricking the user into adding a file whose filename contains a non-default code page and non-ANSI characters, as demonstrated using a Chinese filename, possibly due to buffer expansion when using the WideCharToMultiByte API. NOTE: it is not clear whether this problem can be exploited for code execution. If not, then perhaps the user-assisted nature of the attack should exclude the issue from inclusion in CVE.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2005-4474 is an old WinRAR 3.51 flaw triggered when a user adds a specially named file to an archive. The reported impact is a crash, with possible arbitrary code execution, but the CVE record says code execution is unclear. This is user-assisted and not listed as actively exploited in KEV. Exposure appears limited to systems still running WinRAR 3.51 where users may archive attacker-supplied files with crafted internationalized filenames. The provided affected-product metadata is sparse, but the CVE description specifically names WinRAR 3.51. Treat as a legacy hygiene risk, not an emergency, unless WinRAR 3.51 remains deployed in sensitive workflows. The practical business action is to find and remove outdated installations rather than launch a broad incident response. Mitigation focus: Inventory endpoints for WinRAR 3.51 and prioritize removal or upgrade.; Check vendor guidance for supported fixed versions before remediation.; Avoid archiving untrusted files with unusual non-ANSI filenames on affected systems..

Prepared

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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2005-4474 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
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
1Source links

CVSS and timeline data

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

Source materials

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.