CVE-2005-1178
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 Oracle Forms 10g allows remote attackers to execute arbitrary SQL commands via the Query/Where feature.
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 confidenceSQL injection vulnerability in Oracle Forms 10g allows remote attackers to execute arbitrary SQL commands through the Query/Where feature, potentially allowing unauthorized data access or manipulation.
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= 3.0= 4.5= 5.0= 6.0= 6i= 9i= 10gCVSS 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 Oracle Forms installation and versionCheck for Oracle Forms installation directory (typically ORACLE_HOME/forms) and locate the forms executable or version file. Run 'formsweb.cfg' configuration check or query the Oracle Forms services registry if available.Affected if The installed version matches 3.0, 4.5, 5.0, 6.0, 6i, 9i, or 10g
-
Verify Query/Where feature is accessibleReview the Oracle Forms configuration files (formsweb.cfg, default.env) to determine if the Query/Where feature is enabled for web or client-server deployments. Check if forms are configured to allow user-entered queries.Affected if Query/Where functionality is enabled and exposed to end users in the Forms application configuration
-
Check Forms server exposureExamine the Oracle Forms servlet or listener configuration (usually in formsweb.cfg or oc4j configuration) to determine if the Forms server is accessible over HTTP/HTTPS to remote users.Affected if The Oracle Forms server is exposed to network/remote access without proper authentication restrictions on the Query/Where function
-
Review application-level access controlsInspect the specific Forms modules (.fmb files) to see if custom restrictions exist on the WHEN-NEW-FORM-INSTANCE trigger or other mechanisms that control access to the Query/Where feature.Affected if No application-level restrictions are implemented within the Forms modules to prevent arbitrary SQL injection through Query/Where
A user is affected if they are running any of the listed Oracle Forms versions (3.0 through 10g) with the Query/Where feature enabled and accessible to users, particularly over remote/network connections.
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 Oracle Critical Patch Updates for this vulnerability; if patches are unavailable for this legacy version, consider disabling the Query/Where feature or upgrading to a supported Oracle Forms version.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1178 — 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-2005-1178 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