mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-07-29 05:56:59 +00:00
187 lines
7.0 KiB
JSON
187 lines
7.0 KiB
JSON
{
|
|
"CVE_data_meta": {
|
|
"ASSIGNER": "cve@mitre.org",
|
|
"ID": "CVE-2006-0435",
|
|
"STATE": "PUBLIC"
|
|
},
|
|
"affects": {
|
|
"vendor": {
|
|
"vendor_data": [
|
|
{
|
|
"product": {
|
|
"product_data": [
|
|
{
|
|
"product_name": "n/a",
|
|
"version": {
|
|
"version_data": [
|
|
{
|
|
"version_value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
},
|
|
"vendor_name": "n/a"
|
|
}
|
|
]
|
|
}
|
|
},
|
|
"data_format": "MITRE",
|
|
"data_type": "CVE",
|
|
"data_version": "4.0",
|
|
"description": {
|
|
"description_data": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "Unspecified vulnerability in Oracle PL/SQL (PLSQL), as used in Database Server DS 9.2.0.7 and 10.1.0.5, Application Server 1.0.2.2, 9.0.4.2, 10.1.2.0.2, 10.1.2.1.0, and 10.1.3.0.0, E-Business Suite and Applications 11.5.10, and Collaboration Suite 10.1.1, 10.1.2.0, 10.1.2.1, and 9.0.4.2, allows attackers to bypass the PLSQLExclusion list and access excluded packages and procedures, aka Vuln# PLSQL01."
|
|
}
|
|
]
|
|
},
|
|
"problemtype": {
|
|
"problemtype_data": [
|
|
{
|
|
"description": [
|
|
{
|
|
"lang": "eng",
|
|
"value": "n/a"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references": {
|
|
"reference_data": [
|
|
{
|
|
"name": "19712",
|
|
"refsource": "SECUNIA",
|
|
"url": "http://secunia.com/advisories/19712"
|
|
},
|
|
{
|
|
"name": "18621",
|
|
"refsource": "SECUNIA",
|
|
"url": "http://secunia.com/advisories/18621"
|
|
},
|
|
{
|
|
"name": "19859",
|
|
"refsource": "SECUNIA",
|
|
"url": "http://secunia.com/advisories/19859"
|
|
},
|
|
{
|
|
"name": "20060202 The History of the Oracle PLSQL Gateway Flaw",
|
|
"refsource": "BUGTRAQ",
|
|
"url": "http://www.securityfocus.com/archive/1/423819/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "20060125 Workaround for unpatched Oracle PLSQL Gateway flaw",
|
|
"refsource": "BUGTRAQ",
|
|
"url": "http://www.securityfocus.com/archive/1/423029/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "402",
|
|
"refsource": "SREASON",
|
|
"url": "http://securityreason.com/securityalert/402"
|
|
},
|
|
{
|
|
"name": "http://www.oracle.com/technetwork/topics/security/cpuapr2006-090826.html",
|
|
"refsource": "CONFIRM",
|
|
"url": "http://www.oracle.com/technetwork/topics/security/cpuapr2006-090826.html"
|
|
},
|
|
{
|
|
"name": "1015544",
|
|
"refsource": "SECTRACK",
|
|
"url": "http://securitytracker.com/id?1015544"
|
|
},
|
|
{
|
|
"name": "20060131 Re: Workaround for unpatched Oracle PLSQL Gateway flaw",
|
|
"refsource": "BUGTRAQ",
|
|
"url": "http://www.securityfocus.com/archive/1/423673/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "ADV-2006-1571",
|
|
"refsource": "VUPEN",
|
|
"url": "http://www.vupen.com/english/advisories/2006/1571"
|
|
},
|
|
{
|
|
"name": "ADV-2006-0338",
|
|
"refsource": "VUPEN",
|
|
"url": "http://www.vupen.com/english/advisories/2006/0338"
|
|
},
|
|
{
|
|
"name": "16384",
|
|
"refsource": "BID",
|
|
"url": "http://www.securityfocus.com/bid/16384"
|
|
},
|
|
{
|
|
"name": "403",
|
|
"refsource": "SREASON",
|
|
"url": "http://securityreason.com/securityalert/403"
|
|
},
|
|
{
|
|
"name": "SSRT061148",
|
|
"refsource": "HP",
|
|
"url": "http://www.securityfocus.com/archive/1/432267/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "oracle-plsql-command-execution(24363)",
|
|
"refsource": "XF",
|
|
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/24363"
|
|
},
|
|
{
|
|
"name": "20060125 Workaround for unpatched Oracle PLSQL Gateway flaw",
|
|
"refsource": "FULLDISC",
|
|
"url": "http://lists.grok.org.uk/pipermail/full-disclosure/2006-January/041742.html"
|
|
},
|
|
{
|
|
"name": "20060202 More on the workaround for the unpatched Oracle PLSQL Gateway flaw",
|
|
"refsource": "BUGTRAQ",
|
|
"url": "http://www.securityfocus.com/archive/1/423822/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "20060208 Re: Workaround for unpatched Oracle PLSQL Gateway flaw",
|
|
"refsource": "BUGTRAQ",
|
|
"url": "http://www.securityfocus.com/archive/1/424394/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "20060202 The History of the Oracle PLSQL Gateway Flaw",
|
|
"refsource": "FULLDISC",
|
|
"url": "http://lists.grok.org.uk/pipermail/full-disclosure/2006-February/041898.html"
|
|
},
|
|
{
|
|
"name": "http://www.oracle.com/technology/deploy/security/pdf/public_vuln_to_advisory_mapping.html",
|
|
"refsource": "MISC",
|
|
"url": "http://www.oracle.com/technology/deploy/security/pdf/public_vuln_to_advisory_mapping.html"
|
|
},
|
|
{
|
|
"name": "ADV-2006-1397",
|
|
"refsource": "VUPEN",
|
|
"url": "http://www.vupen.com/english/advisories/2006/1397"
|
|
},
|
|
{
|
|
"name": "22719",
|
|
"refsource": "OSVDB",
|
|
"url": "http://www.osvdb.org/22719"
|
|
},
|
|
{
|
|
"name": "HPSBMA02113",
|
|
"refsource": "HP",
|
|
"url": "http://www.securityfocus.com/archive/1/432267/100/0/threaded"
|
|
},
|
|
{
|
|
"name": "VU#169164",
|
|
"refsource": "CERT-VN",
|
|
"url": "http://www.kb.cert.org/vuls/id/169164"
|
|
},
|
|
{
|
|
"name": "20060202 More on the workaround for the unpatched Oracle PLSQL Gateway flaw",
|
|
"refsource": "FULLDISC",
|
|
"url": "http://lists.grok.org.uk/pipermail/full-disclosure/2006-February/041899.html"
|
|
},
|
|
{
|
|
"name": "1015961",
|
|
"refsource": "SECTRACK",
|
|
"url": "http://securitytracker.com/id?1015961"
|
|
}
|
|
]
|
|
}
|
|
} |