CVE-1999-0949
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 canuum program for Canna input system allows local users to gain root privileges.
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 · moderate confidenceBuffer overflow vulnerability in the canuum program of the Canna Japanese input method system allows local attackers to execute arbitrary code with elevated privileges by overflowing a buffer, potentially achieving root access.
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= 5.3= 6.2= 6.3= 6.4= 6.5= 2.6= 7.0all versions= 5.7= 4.2CVSS 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Check if Canna input method is installedLook for the Canna package or canuum binary on the system. Common paths include /usr/bin/cannau, /usr/local/bin/cannau, or check package manager for Canna-related packages.Affected if The Canna Japanese input method system is present on the system.
-
Verify canuum binary existsSearch for the canuum executable using 'find / -name canuum -type f 2>/dev/null' or check common binary directories.Affected if The canuum binary file exists on the system.
-
Confirm OS version matches affected releasesRun 'uname -a' or check /etc/os-release for Linux, or 'uname -rv' for Solaris/IRIX. Compare against: IRIX 5.3, 6.2-6.5; Solaris 2.6, 7.0; SunOS 5.7 or all SunOS versions; Turbolinux 4.2.Affected if The operating system version matches one of the affected versions listed.
-
Check if canuum has setuid permissionsRun 'ls -la' on the canuum binary path. Look for 's' in the owner permissions field (e.g., -rwsr-xr-x) which indicates setuid bit is set.Affected if The canuum binary has setuid or setgid permissions enabled, allowing it to run with elevated privileges.
The environment is affected if Canna input method with the canuum program is installed on a matching OS version and canuum has setuid permissions, allowing local privilege escalation.
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 dataRemove the Canna input system if not required, or apply any available vendor patches; restrict local user access to trusted personnel only since this is a local privilege escalation vulnerability.
- Consultation2.0 h
- Implementation3.0 h
- Testing1.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,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0949 — 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-1999-0949 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