CVE-2009-3395
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 AutoVue component in Oracle E-Business Suite 19.3.2 allows remote attackers to affect availability via unknown 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 · low confidenceThis is an unspecified vulnerability in the AutoVue component of Oracle E-Business Suite 19.3.2. Remote unauthenticated attackers can exploit unknown vectors to impact system availability, likely through a denial-of-service condition. The vulnerability affects only availability (CVSS auxiliary vector), not confidentiality or integrity.
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= 19.3.2CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 E-Business Suite installationCheck for Oracle E-Business Suite installation by looking for typical installation directories such as $ORACLE_HOME or C:\Oracle\EBS, or query the system for Oracle-related software via inventory toolsAffected if Oracle E-Business Suite is installed and the version is exactly 19.3.2
-
Verify the exact E-Business Suite versionRun the command to display the Oracle E-Business Suite version, typically through Oracle Application Manager or by querying the database version tables (FND_PRODUCT_GROUPS or similar)Affected if The installed version is exactly 19.3.2 (not higher or lower)
-
Determine if AutoVue component is installedCheck for AutoVue component by examining the Oracle E-Business Suite installed modules, looking for AutoVue in the product inventory or checking for AutoVue-specific directories under the EBS homeAffected if AutoVue component is listed as installed in the Oracle E-Business Suite product inventory
-
Check if AutoVue service is runningIdentify running processes or services related to AutoVue (such as autovue, AutoVue40, or similar process names), or check for listening ports typically used by AutoVue (common ports include 8089, 8090, or custom ports)Affected if An AutoVue process or service is running or an AutoVue-related port is listening
You are affected if Oracle E-Business Suite version 19.3.2 is installed AND the AutoVue component is present and enabled on your system.
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's relevant security patch for the AutoVue component; if unavailable, consider network segmentation to restrict access to the AutoVue service and monitor for unusual availability issues.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-3395 — 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-3395 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