CVE-2013-0799
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 the Mozilla Maintenance Service in Mozilla Firefox before 20.0, Firefox ESR 17.x before 17.0.5, Thunderbird before 17.0.5, and Thunderbird ESR 17.x before 17.0.5 on Windows allows local users to gain privileges via crafted arguments.
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 vulnerability in the Mozilla Maintenance Service on Windows allows local unprivileged users to execute arbitrary code with elevated privileges via crafted command-line arguments. The flaw exists in how the service handles arguments passed to it, leading to heap-based buffer overflow that can be exploited for local privilege escalation.
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<= 19.0.2= 19.0= 19.0.1= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4CVSS 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.
-
Verify Windows operating systemCheck if the system is running Windows. This vulnerability only affects Windows hosts. Run 'systeminfo' on Windows or check the OS name.Affected if The system is running Windows and the Mozilla Maintenance Service is installed.
-
Locate the Mozilla Maintenance ServiceOn Windows, check if the Mozilla Maintenance Service exists. Look for 'Mozilla Maintenance Service' in Windows Services (services.msc) or check for the service binary in the Firefox or Thunderbird installation directory.Affected if The Mozilla Maintenance Service is present on the system.
-
Check installed Firefox versionOpen Firefox, go to Help > About Firefox, or check the version from the Windows registry under HKLM\Software\Mozilla\Mozilla Firefox\CurrentVersion or HKCU\Software\Mozilla\Mozilla Firefox\CurrentVersion.Affected if The installed Firefox version is 19.0, 19.0.1, 19.0.2, or any 17.0.x version through 17.0.4.
-
Check installed Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird, or check the version from the Windows registry under HKLM\Software\Mozilla\Thunderbird\Version or HKCU\Software\Mozilla\Thunderbird\Version.Affected if The installed Thunderbird version (standard or ESR) is 17.0, 17.0.1, 17.0.2, 17.0.3, or 17.0.4.
-
Confirm the Maintenance Service is runningOpen Services (services.msc), locate 'Mozilla Maintenance Service', and check its Status column. It is running if Status shows 'Running'.Affected if The Mozilla Maintenance Service is installed and currently running on a vulnerable Firefox or Thunderbird version.
A user is affected if running Windows with Firefox versions 19.0-19.0.2 or 17.0-17.0.4, or Thunderbird/Thunderbird ESR versions 17.0-17.0.4, and the Mozilla Maintenance Service is installed and running.
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 dataApply vendor-supplied updates: upgrade Firefox to 20.0 or later, Firefox ESR to 17.0.5 or later, Thunderbird to 17.0.5 or later, or Thunderbird ESR to 17.0.5 or later. Alternatively, disable the Mozilla Maintenance Service if not required.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0799 — 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-0799 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