Oracle Outside In Technology 8.5.3 Outside In Filters access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Oracle Outside In Technology 8.5.3. This impacts an unknown function of the component Outside In Filters. The manipulation leads to access control. This vulnerability is listed as CVE-2018-3219. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as critical, has been found in Oracle Outside In Technology 8.5.3 (Programming Tool Software). This issue affects some unknown processing of the component Outside In Filters. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, and availability.
The bug was discovered 10/16/2018. The weakness was presented 10/16/2018 with Zero Day Initiative as Oracle Critical Patch Update Advisory - October 2018 as confirmed advisory (Website). The advisory is shared at oracle.com. The identification of this vulnerability is CVE-2018-3219 since 12/15/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 105603†). See VDB-90449, VDB-91385, VDB-91680 and VDB-91681 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.oracle.com
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.1
VulDB Temp Score: 6.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Oracle): 7.1
Vendor Vector (Oracle): 🔍
NVD Base Score: 7.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
12/15/2017 🔍10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/17/2018 🔍
05/26/2023 🔍
Sources
Vendor: oracle.comAdvisory: Oracle Critical Patch Update Advisory - October 2018
Organization: Zero Day Initiative
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2018-3219 (🔍)
GCVE (CVE): GCVE-0-2018-3219
GCVE (VulDB): GCVE-100-125453
SecurityFocus: 105603 - Oracle Outside In Technology Multiple Security Vulnerabilities
See also: 🔍
Entry
Created: 10/17/2018 08:40Updated: 05/26/2023 09:26
Changes: 10/17/2018 08:40 (71), 04/03/2020 09:41 (6), 05/26/2023 09:26 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.