CVE-2010-1733
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 · uneditedMultiple SQL injection vulnerabilities in OCS Inventory NG before 1.02.3 allow remote attackers to execute arbitrary SQL commands via (1) multiple inventory fields to the search form, reachable through index.php; or (2) the "Software name" field to the "All softwares" search form, reachable through index.php. NOTE: the provenance of this information is unknown; the details are obtained solely from third party information.
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 vulnerabilities in OCS Inventory NG allow remote attackers to inject arbitrary SQL commands via search form fields in index.php. Affected parameters include multiple inventory fields and the 'Software name' field in the 'All softwares' search form.
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.02.1= 1.0= 1.01= 1.02CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 OCS Inventory NG versionCheck the version file or log in to the admin web interface and look for the version number displayed in the footer or 'About' section. Also check files like version.txt or config.php for version information.Affected if The installed version is 1.0, 1.01, 1.02, or any version <= 1.02.1
-
Confirm web interface is accessibleVerify that the OCS Inventory NG web interface (index.php) is reachable via HTTP/HTTPS. This SQL injection requires the web application to be accessible.Affected if The web interface is exposed and reachable over the network
-
Locate vulnerable search form codeExamine the index.php file in the OCS web directory. Look for the 'All softwares' search form handling code and the 'Software name' parameter processing logic.Affected if The index.php file contains search form handling code that processes user input without apparent parameterization
-
Check for SQL injection vulnerability in search parametersReview the code handling the search form inputs in index.php, specifically looking for direct insertion of request parameters into SQL queries without using parameterized queries or input sanitization.Affected if Code in index.php passes search form parameters directly into SQL queries without prepared statements or proper escaping
A user is affected if they are running OCS Inventory NG versions 1.0, 1.01, 1.02, or <= 1.02.1 with the web interface accessible and the vulnerable search form code present in index.php.
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 dataUpgrade to OCS Inventory NG 1.02.3 or later, and implement parameterized queries or proper input validation on all search form fields to prevent SQL injection.
- 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-2010-1733 — 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-2010-1733 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