CVE-2021-2035
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 RDBMS Scheduler component of Oracle Database Server. Supported versions that are affected are 12.1.0.2, 12.2.0.1, 18c and 19c. Easily exploitable vulnerability allows low privileged attacker having Export Full Database privilege with network access via Oracle Net to compromise RDBMS Scheduler. Successful attacks of this vulnerability can result in takeover of RDBMS Scheduler. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
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 or privilege escalation vulnerability in Oracle RDBMS Scheduler allows low-privileged users with Export Full Database privilege to gain full control of the Scheduler component via network exploit, achieving complete confidentiality, integrity, and availability compromise.
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.1.0.2= 12.2.0.1= 18c= 19cCVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 database versionExecute SELECT VERSION FROM V$INSTANCE; or SELECT BANNER FROM V$VERSION WHERE BANNER LIKE 'Oracle Database%';Affected if Version matches 12.1.0.2, 12.2.0.1, 18c, or 19c
-
Verify Export Full Database privilege existsExecute SELECT GRANTEE, PRIVILEGE FROM DBA_SYS_PRIVS WHERE PRIVILEGE = 'EXPORT FULL DATABASE'; to list users with this privilege, or check current user privileges via SELECT * FROM SESSION_PRIVS;Affected if Any low-privileged user account has EXPORT FULL DATABASE privilege granted
-
Confirm Scheduler component is accessibleExecute SELECT OWNER, JOB_NAME, JOB_TYPE FROM DBA_SCHEDULER_JOBS; to enumerate existing Scheduler jobs, or test access via DBMS_SCHEDULER package availabilityAffected if Scheduler jobs exist or DBMS_SCHEDULER is accessible to the privileged user
-
Check for vulnerable job definitionsReview output from SELECT OWNER, JOB_NAME, JOB_TYPE, PROGRAM_NAME FROM DBA_SCHEDULER_JOBS WHERE JOB_TYPE IN ('EXECUTABLE','CHAIN'); for jobs that execute external programs or chainsAffected if Scheduler jobs of type EXECUTABLE or CHAIN are defined and the Export Full Database user has permission to modify them
You are affected if your Oracle Database version is 12.1.0.2, 12.2.0.1, 18c, or 19c AND a low-privileged user has EXPORT FULL DATABASE privilege while Scheduler jobs are accessible to that user.
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) addressing CVE-2021-2035 to affected versions (12.1.0.2, 12.2.0.1, 18c, 19c); review and audit Scheduler job definitions and associated privileges post-patch.
- Consultation6.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-2035 — 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-2021-2035 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