CVE-2009-1993
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 · uneditedUnspecified vulnerability in the Application Express component in Oracle Database 3.0.1 allows remote authenticated users to affect confidentiality and integrity, related to FLOWS_030000.WWV_EXECUTE_IMMEDIATE.
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 confidenceThis is a vulnerability in Oracle Application Express (APEX) 3.0.1 affecting the WWV_EXECUTE_IMMEDIATE procedure in the FLOWS_030000 schema. The function likely allows execution of dynamic SQL and is vulnerable to injection or improper privilege escalation, enabling authenticated users to access or modify data beyond their intended permissions.
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.1CVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
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 APEX versionConnect to the database as a DBA user and query the APEX version. Run: SELECT version FROM apex_version; or check dba_registry for component name 'Oracle Application Express'.Affected if The version returned is exactly 3.0.1, as this is the only affected version listed.
-
Confirm FLOWS_030000 schema existsQuery dba_users or all_users to verify the FLOWS_030000 schema exists in the database. Run: SELECT username FROM dba_users WHERE username = 'FLOWS_030000';Affected if The FLOWS_030000 schema exists, which indicates APEX 3.0.1 is installed.
-
Verify vulnerable procedure existsQuery all_objects to check if WWV_EXECUTE_IMMEDIATE exists in the FLOWS_030000 schema. Run: SELECT object_name, object_type FROM all_objects WHERE owner = 'FLOWS_030000' AND object_name = 'WWV_EXECUTE_IMMEDIATE';Affected if The procedure WWV_EXECUTE_IMMEDIATE is present in the FLOWS_030000 schema.
-
Check APEX workspace and user authenticationDetermine if APEX workspaces are configured and if users have authenticated access. Query apex_workspace_apex_users or check if HTTP authentication to APEX is enabled.Affected if APEX is accessible with authenticated user accounts, which is required for exploitation of this vulnerability.
A user is affected if APEX version 3.0.1 is installed with the FLOWS_030000 schema and WWV_EXECUTE_IMMEDIATE procedure present, and the environment accepts authenticated APEX user 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 Update (CPU) for July 2009 or subsequent patch that addresses CVE-2009-1993. Alternatively, upgrade to a newer APEX version with security fixes. Also validate that database user privileges are properly scoped to least-privilege principles.
- 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-2009-1993 — 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-2009-1993 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