CVE-2013-7420
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBuffer overflow in Hancom Office 2010 SE allows remote attackers to execute arbitrary via a long string in the Text attribute in a TEXTART XML element in an HML file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBuffer overflow in Hancom Office 2010 SE's XML parser for TEXTART elements allows remote code execution via a malicious HML file containing an overly long string in the Text attribute.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.5.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Hancom Office 2010 SE installationCheck for Hancom Office 2010 SE in installed programs list (Windows: Control Panel > Programs and Features, or run 'wmic product get name,version'), or look for Hancom Office executables in Program FilesAffected if Hancom Office 2010 SE is installed
-
Confirm installed version is 8.5.8Run 'wmic product where "name like 'Hancom%'" get name,version' or check the program's About/Help dialog for version informationAffected if Installed version equals 8.5.8 exactly
-
Check for HML file handling capabilitySearch for .hml file associations in Windows Registry under HKCR\.hml or check if HML files open with Hancom Office; also locate hanzipc.dll or similar parser DLLs in the Hancom installation directory (typically C:\Program Files\Hancom\Hancom Office 2010 SE\)Affected if HML file handler is registered or XML parser DLLs exist indicating the vulnerable component is present
-
Inspect TEXTART parsing moduleExamine the program's installation folder for XML-related DLLs (such as hwpml*.dll, xmlparser*.dll, or similar) that handle TEXTART element parsing; use Process Monitor or check file timestamps to confirm they are part of version 8.5.8Affected if TEXTART XML parser module exists in the Hancom Office installation directory
If Hancom Office 2010 SE version 8.5.8 is installed with HML file handling enabled and the TEXTART XML parser component is present, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid opening HML files from untrusted or unknown sources; contact Hancom for a security patch to properly bounds-check the TEXTART attribute parsing.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7420 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-7420 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data