CVE-2008-1546
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 · uneditedservlet/MIMEReceiveServlet in the web controller for Mitsubishi Electric GB-50 and GB-50A air-conditioning control systems allows remote attackers to cause a denial of service (air-conditioning outage) via an XML document containing a setRequest command.
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 confidenceThe MIMEReceiveServlet in Mitsubishi Electric GB-50 and GB-50A air-conditioning web controllers fails to properly validate incoming XML documents containing setRequest commands, allowing remote attackers to crash the servlet and cause complete air-conditioning system outage.
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= 50= 50aCVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify the air-conditioning controller modelAccess the web controller administrative interface or check device labeling/documentation to confirm the exact model number (GB-50 or GB-50A)Affected if The model is a Mitsubishi Electric GB-50 or GB-50A unit
-
Locate the web controller interfaceAttempt to access the web-based management interface on the device (typically HTTP on ports 80 or 8080; consult device documentation for default IP and port)Affected if The web controller interface is accessible over the network
-
Check for MIMEReceiveServlet availabilityAttempt to access the MIMEReceiveServlet endpoint via URL path such as /servlet/MIMEReceiveServlet or /MIMEReceiveServlet (or consult product documentation for exact servlet path)Affected if The MIMEReceiveServlet endpoint responds to requests, indicating the vulnerable servlet is enabled
-
Verify XML-based control interface exposureConfirm that the servlet accepts XML-based setRequest commands by inspecting the web controller configuration or attempting a test request with a crafted XML payload containing setRequest elementsAffected if The servlet processes incoming XML documents with setRequest commands without proper validation
The environment is affected if it contains a Mitsubishi Electric GB-50 or GB-50A air-conditioning web controller with an exposed MIMEReceiveServlet that accepts unauthenticated XML setRequest commands.
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 dataIsolate the air-conditioning control systems on a restricted network segment, implement firewall rules to limit access to the web controller interface, and contact Mitsubishi Electric for firmware updates or patches to address the input validation flaw.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-1546 — 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-2008-1546 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