CVE-2021-47774
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 · uneditedKingdia CD Extractor 3.0.2 contains a buffer overflow vulnerability in the registration name field that allows attackers to execute arbitrary code. Attackers can craft a malicious payload exceeding 256 bytes to overwrite Structured Exception Handler and gain remote code execution through a bind shell.
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 confidenceKingdia CD Extractor 3.0.2 contains a buffer overflow in the registration name field where a payload exceeding 256 bytes can overwrite the Structured Exception Handler (SEH), enabling arbitrary code execution through a bind shell for remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate Kingdia CD Extractor installationSearch for 'Kingdia CD Extractor' in Windows Add/Remove Programs, or check common installation directories such as C:\Program Files\Kingdia or C:\Program Files (x86)\Kingdia. Also search for the executable file 'Kingdia CD Extractor.exe' on the system.Affected if The application is found installed on the system.
-
Determine installed versionRight-click the Kingdia CD Extractor executable, select Properties, and inspect the Version tab to obtain the precise version number. Alternatively, check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for the installed version entry.Affected if The version displayed is 3.0.2.
-
Verify registration feature existsLaunch Kingdia CD Extractor and navigate to the registration or 'Enter Registration Code' option in the Help or main menu. This is the feature that contains the vulnerable registration name input field.Affected if The application provides a registration name input field.
-
Assess exposure to crafted inputReview whether any untrusted user or external entity can supply input to the registration name field. This could occur through: (1) manual entry by any user of the system, or (2) a file or script that loads a crafted registration name into the application.Affected if A user or process can input more than 256 characters into the registration name field.
A user is affected if Kingdia CD Extractor version 3.0.2 is installed and the registration name field can accept more than 256 bytes of input, allowing SEH overwrite and potential code execution.
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 using Kingdia CD Extractor 3.0.2; replace with maintained CD ripping software or, if continued use is required, run the application in an isolated virtual machine with network segmentation to limit exposure.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-47774 — 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-2021-47774 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