mirror of
https://github.com/CVEProject/cvelist.git
synced 2025-08-04 08:44:25 +00:00

Apache CNA) and ensure that the product names are correct and consistent (which in most cases means adding "Apache", but some required more work). Make sure the vendor name is correct. Make sure affected versions matches the text somewhat, although we don't try to make every product write these in the same way, they're not supposed to be totally machine readable. Then make some fixes to the text as required where there are mistakes or inconsistencies or the Apache name isn't mentioned. There are 5 left untouched for now, one is known (where we assigned an issues to an incubator version which came out prior to being part of Apache), and four which need more work.
74 lines
2.8 KiB
JSON
74 lines
2.8 KiB
JSON
{
|
|
"CVE_data_meta" : {
|
|
"ASSIGNER" : "security@apache.org",
|
|
"DATE_PUBLIC" : "2018-09-18T00:00:00",
|
|
"ID" : "CVE-2018-11786",
|
|
"STATE" : "PUBLIC"
|
|
},
|
|
"affects" : {
|
|
"vendor" : {
|
|
"vendor_data" : [
|
|
{
|
|
"product" : {
|
|
"product_data" : [
|
|
{
|
|
"product_name" : "Apache Karaf",
|
|
"version" : {
|
|
"version_data" : [
|
|
{
|
|
"version_value" : "prior to 4.2.0 release"
|
|
}
|
|
]
|
|
}
|
|
}
|
|
]
|
|
},
|
|
"vendor_name" : "Apache Software Foundation"
|
|
}
|
|
]
|
|
}
|
|
},
|
|
"data_format" : "MITRE",
|
|
"data_type" : "CVE",
|
|
"data_version" : "4.0",
|
|
"description" : {
|
|
"description_data" : [
|
|
{
|
|
"lang" : "eng",
|
|
"value" : "In Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the running instance, any user with rights to the Karaf console can pivot and read/write any file on the file system to which the Karaf process user has access. This can be locked down a bit by using chroot to change the root directory to protect files outside of the Karaf install directory; it can be further locked down by defining a security manager policy that limits file system access to those directories beneath the Karaf home that are necessary for the system to run. However, this still allows anyone with ssh access to the Karaf process to read and write a large number of files as the Karaf process user."
|
|
}
|
|
]
|
|
},
|
|
"problemtype" : {
|
|
"problemtype_data" : [
|
|
{
|
|
"description" : [
|
|
{
|
|
"lang" : "eng",
|
|
"value" : "Process Execution"
|
|
}
|
|
]
|
|
}
|
|
]
|
|
},
|
|
"references" : {
|
|
"reference_data" : [
|
|
{
|
|
"name" : "[karaf-dev] 20180918 [SECURITY] New security advisory for CVE-2018-11786 released for Apache Karaf",
|
|
"refsource" : "MLIST",
|
|
"url" : "https://lists.apache.org/thread.html/5b7ac762c6bbe77ac5d9389f093fc6dbf196c36d788e3d7629e6c1d9@%3Cdev.karaf.apache.org%3E"
|
|
},
|
|
{
|
|
"name" : "http://karaf.apache.org/security/cve-2018-11786.txt",
|
|
"refsource" : "CONFIRM",
|
|
"url" : "http://karaf.apache.org/security/cve-2018-11786.txt"
|
|
},
|
|
{
|
|
"name" : "https://issues.apache.org/jira/browse/KARAF-5427",
|
|
"refsource" : "CONFIRM",
|
|
"url" : "https://issues.apache.org/jira/browse/KARAF-5427"
|
|
}
|
|
]
|
|
}
|
|
}
|