Id:
CVE-2016-10374
Comment
:
perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.
CVSSv2 Score:
2.1
Access vector:
|
LOCAL
|
Access complexity:
|
LOW
|
Authentication:
|
NONE
|
Confidentiality impact:
|
NONE
|
Integrity impact:
|
PARTIAL
|
Availability impact:
|
NONE
|
CVSSv2 Vector:
AV:L/AC:L/Au:N/C:N/I:P/A:N
CVSSv3 Score:
5.5
Attack vector:
|
LOCAL
|
Attack complexity:
|
LOW
|
Privileges required:
|
LOW
|
User interaction:
|
NONE
|
Scope:
|
UNCHANGED
|
Confidentiality impact:
|
NONE
|
Integrity impact:
|
HIGH
|
Availability impact:
|
NONE
|
CVSSv3 Vector:
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
References: