I/Librarian up to 4.6/4.7 temp.php Reflected cross site scripting

Summaryinfo

A vulnerability has been found in I and Librarian up to 4.6/4.7 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file temp.php. The manipulation leads to cross site scripting (Reflected). This vulnerability is uniquely identified as CVE-2017-1000236. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in I and Librarian up to 4.6/4.7. It has been rated as problematic. This issue affects an unknown part of the file temp.php. The manipulation with an unknown input leads to a cross site scripting vulnerability (Reflected). Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:

I, Librarian version <=4.6 & 4.7 is vulnerable to Reflected Cross-Site Scripting in the temp.php resulting in an attacker being able to inject malicious client side scripting which will be executed in the browser of users if they visit the manipulated site.

The bug was discovered 05/09/2017. The weakness was disclosed 11/17/2017 (Website). The advisory is shared at sec-consult.com. The identification of this vulnerability is CVE-2017-1000236 since 11/16/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. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 191 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:temp.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-109635, VDB-109636 and VDB-109638 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• I
• Librarian

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion