CVE-2012-0912
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 · uneditedSQL injection vulnerability in Stoneware webNetwork before 6.0.8.0 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.
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 confidenceSQL injection vulnerability in Stoneware webNetwork versions prior to 6.0.8.0 allows remote attackers to inject malicious SQL statements through unspecified input vectors, potentially enabling unauthorized database access, data exfiltration, or modification of database contents.
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<= 6.0.7.0= 6.0.5.0CVSS 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.
-
Identify installed webNetwork versionLocate the installed version through the product's About page, help menu, or version information in the administrative console. Check any installation documentation or release notes for the exact version number currently deployed.Affected if The version is 6.0.7.0 or lower, or specifically 6.0.5.0
-
Compare version against affected rangeReview the identified version against the affected ranges: any version less than or equal to 6.0.7.0, or exactly version 6.0.5.0.Affected if The installed version falls within <= 6.0.7.0 or equals 6.0.5.0
-
Confirm webNetwork service is running and accessibleVerify that the webNetwork application service is operational and network-accessible, as this remote SQL injection requires the application to be accepting connections.Affected if The service is running and externally or internally accessible on any version within the affected range
-
Review application input handlingInspect the webNetwork configuration and logs for any evidence of user-supplied input being processed through database queries without parameterized query handling.Affected if The application processes user input through SQL queries without prepared statements or input validation, and runs a vulnerable version
A user is affected if Stoneware webNetwork version 6.0.7.0 or lower (including 6.0.5.0) is installed and the web application service is running and accessible, as this enables remote SQL injection exploitation.
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 dataPrimary remediation is to upgrade to webNetwork version 6.0.8.0 or later; as an interim compensating control, implement strict input validation and ensure all database queries use parameterized queries or prepared statements.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0912 — 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-0912 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