CVE-2012-6427
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 · uneditedThe Carlo Gavazzi EOS-Box does not check the validity of the data before executing queries. By accessing the SQL table of certain pages that do not require authentication, attackers can leak information from the device. This could allow the attacker to compromise confidentiality.
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 Carlo Gavazzi EOS-Box contains an SQL injection vulnerability where the web interface does not validate input data before executing SQL queries. Attackers can access unauthenticated pages to inject malicious SQL queries and exfiltrate data from the device's underlying database, compromising confidentiality.
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<= 1.0.0all versionsCVSS 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.
-
Confirm device modelIdentify if the target system is a Carlo Gavazzi EOS-Box Photovoltaic Monitoring System by checking the device label, web interface banner, or SNMP/sysinfo data for 'EOS-Box' or 'Carlo Gavazzi' brandingAffected if The device is not a Carlo Gavazzi EOS-Box Photovoltaic Monitoring System
-
Check firmware versionAccess the device's web interface or administrative console and locate the firmware version information, typically found in 'About', 'Status', or 'System Information' pagesAffected if Firmware version is 1.0.0 or lower, or if the version cannot be determined but the product is confirmed as EOS-Box (all versions affected)
-
Verify web interface is exposedAttempt to access the device's web interface over HTTP/HTTPS on common ports (80, 443, 8080) from a network perspectiveAffected if The web interface is reachable and responds with the EOS-Box login or status page
-
Identify unauthenticated access pointsReview the web application for pages accessible without authentication, such as login, status, or diagnostic endpoints, that accept user input via query parameters or form fieldsAffected if Any unauthenticated page accepts user-supplied input (query parameters, form fields) that could be used to inject SQL queries
You are affected if the target is a Carlo Gavazzi EOS-Box Photovoltaic Monitoring System with web interface access and any unauthenticated input fields are present.
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 any vendor-supplied firmware update; if unavailable, isolate the device on a restricted network segment and implement web application firewall rules to block SQL injection patterns.
- 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-2012-6427 — 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-2012-6427 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