CVE-2022-21477
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 · uneditedVulnerability in the Oracle Applications Framework product of Oracle E-Business Suite (component: Attachments, File Upload). Supported versions that are affected are 12.2.6-12.2.11. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Applications Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Applications Framework, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Applications Framework accessible data as well as unauthorized read access to a subset of Oracle Applications Framework accessible data. CVSS 3.1 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
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 confidenceInsecure file upload vulnerability in Oracle Applications Framework's Attachments/File Upload component. Allows low-privileged attackers with network access via HTTP to perform unauthorized read, insert, update, and delete operations on a subset of accessible data. The attack requires human interaction and can impact additional products due to scope change.
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>= 12.2.6, <= 12.2.11CVSS 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
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Verify Oracle Applications Framework is installedQuery the Oracle E-Business Suite database for the OAF version using SELECT product_version FROM fnd_product_groups WHERE product = 'OAF'; or check the OAF About page in the application (Navigate to Oracle Applications Manager > About).Affected if The OAF version falls within 12.2.6 through 12.2.11 inclusive.
-
Confirm Oracle E-Business Suite release versionRun SELECT release_name FROM fnd_product_groups; or check the release version displayed in the Oracle Applications Manager login page or under Help > About Oracle Application Manager in the browser.Affected if The base release version is between 12.2.6 and 12.2.11.
-
Determine if the Attachments/File Upload component is configuredCheck the Oracle Applications Framework configuration files (specifically the OA.jsp or page definitions that reference the /oa_servlets/ofsAttachUpload or similar attachment upload servlets) or review the Oracle E-Business Suite functional setup for the Attachments feature.Affected if The Attachments feature is enabled and the file upload servlet is accessible.
-
Verify network exposure of the upload endpointReview the Oracle E-Business Suite web entry point configuration (Oracle HTTP Server or Oracle Web Listener) to confirm if the /OA_HTML/ directory and attachment servlet URLs are exposed to the network via HTTP (not only HTTPS).Affected if The file upload servlet is accessible over HTTP without additional authentication layers beyond standard OAF session auth.
-
Confirm if low-privileged user accounts exist with attachment accessQuery the database for users with responsibility or role assignments that include access to the Attachments functionality, such as SELECT DISTINCT fu.user_name FROM fnd_user fu JOIN fnd_user_resp_groups fur ON fu.user_id = fur.user_id JOIN fnd_responsibilities fr ON fur.responsibility_id = fr.responsibility_id WHERE fr.responsibility_name LIKE '%Attach%';Affected if Low-privileged users (non-SYSADMIN) have responsibilities that grant access to the Attachments feature.
You are affected if Oracle Applications Framework version is between 12.2.6 and 12.2.11, the Attachments/File Upload component is enabled, and low-privileged users can access the upload functionality over the network.
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) containing the fix for this vulnerability. Implement strict file type validation and content inspection on upload functionality as a compensating control until patch can be applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21477 — 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-2022-21477 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