젠킨스의 소프트웨어에 의해 중단 통합의 개방 악기 플러그인의 큰 숫자는 다른 버그와 취약점을 포함.Vulnerabilities mainly connected with storing of passwords in non-encrypted form. 또한, 젠킨스 '소프트에서 발견 CSRF-공격을 자격 증명을 steaking 및 투입을 허용 CSRF-버그.
빅토르 리치, specialist of NCC Group that tested great number of Jenkins’ plugins, 이러한 문제를 밝혀.
“These tests resulted in more than 100 plugins found vulnerable and several coordinated and responsible public disclosures”, — reports researcher.
As expert explained, though Jenkins encrypts passwords in credentials.xml file, some developers use other methods of data storage. In the majority of cases these decisions do not suggest are encryption. 그 위에, some web-forms, where users input credentials, enable leakage of passwords or secret tokens.
CSRF-vulnerabilities are connected with plugins’ functions, with the use of which users can check credentials and connect to a server. They mostly exist, as developers do not apply POST-requests that prevent attacks with the use of CSRF token.
In the last two years, Jenkins developers released several notifications that describe vulnerabilities in different plugins, including series of bugs, discovered by Gazdag.
Vulnerable plugins interact with a wide circle of services, ...을 포함하여 지저귀다, AWS, VMware 과 Azure. In most cases software was created by side developers that is not connected to vendor, whose software exploits plugin.
언급 한 바와 같이, authors of several plugins have already fixed bugs in their software, though many are still vulnerable. In their turn, Jenkins developers published a vast list of plugins that still are not fixed.