In Apache Derby 10.3.1.4 to 10.14.1.0, a specially-crafted network packet can be used to request the Derby Network Server to boot a database whose location and contents are under the user's control. If the Derby Network Server is not running with a Java Security Manager policy file, the attack is successful. If the server is using a policy file, the policy file must permit the database location to be read for the attack to work. The default Derby Network Server policy file distributed with the affected releases includes a permissive policy as the default Network Server policy, which allows the attack to work.
The MITRE CVE dictionary describes this issue as:
Find out more about CVE-2018-1313 from the MITRE CVE dictionary dictionary and NIST NVD.
NOTE: The following CVSS v3 metrics and score provided are preliminary and subject to review.
CVSS3 Base Score | 7.5 |
---|---|
CVSS3 Base Metrics | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Attack Vector | Network |
Attack Complexity | Low |
Privileges Required | None |
User Interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity Impact | High |
Availability Impact | None |
Platform | Package | State |
---|---|---|
Red Hat Single Sign-On 7 | derby | Not affected |
Red Hat JBoss Fuse 7 | pax-jdbc-derby | Not affected |
Red Hat JBoss Fuse 6 | camel | Not affected |
Red Hat JBoss BRMS 6 | derby | Affected |
Red Hat JBoss BRMS 5 | derby | Will not fix |
Red Hat JBoss BPMS 6 | derby | Affected |