MISP up to 2.4.78 Comment Field CommandHelper.php Persistent cross site scripting

Summaryinfo

A vulnerability has been found in MISP up to 2.4.78 and classified as problematic. The impacted element is an unknown function of the file app/View/Helper/CommandHelper.php of the component Comment Field. Performing a manipulation as part of Comment results in cross site scripting (Persistent). This vulnerability is reported as CVE-2017-13671. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in MISP up to 2.4.78. This affects an unknown part of the file app/View/Helper/CommandHelper.php of the component Comment Field. The manipulation as part of a Comment leads to a cross site scripting vulnerability (Persistent). CWE is classifying the issue as 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. This is going to have an impact on integrity. The summary by CVE is:

app/View/Helper/CommandHelper.php in MISP before 2.4.79 has persistent XSS via comments. It only impacts the users of the same instance because the comment field is not part of the MISP synchronisation.

The bug was discovered 08/24/2017. The weakness was disclosed 08/24/2017 (GitHub Repository). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2017-13671 since 08/24/2017. It is possible to initiate the attack remotely. No form of authentication is needed for 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.

By approaching the search of inurl:app/View/Helper/CommandHelper.php it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.4.79 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 100533†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• MISP

Version

• 2.4.0
• 2.4.1
• 2.4.2
• 2.4.3
• 2.4.4
• 2.4.5
• 2.4.6
• 2.4.7
• 2.4.8
• 2.4.9
• 2.4.10
• 2.4.11
• 2.4.12
• 2.4.13
• 2.4.14
• 2.4.15
• 2.4.16
• 2.4.17
• 2.4.18
• 2.4.19
• 2.4.20
• 2.4.21
• 2.4.22
• 2.4.23
• 2.4.24
• 2.4.25
• 2.4.26
• 2.4.27
• 2.4.28
• 2.4.29
• 2.4.30
• 2.4.31
• 2.4.32
• 2.4.33
• 2.4.34
• 2.4.35
• 2.4.36
• 2.4.37
• 2.4.38
• 2.4.39
• 2.4.40
• 2.4.41
• 2.4.42
• 2.4.43
• 2.4.44
• 2.4.45
• 2.4.46
• 2.4.47
• 2.4.48
• 2.4.49
• 2.4.50
• 2.4.51
• 2.4.52
• 2.4.53
• 2.4.54
• 2.4.55
• 2.4.56
• 2.4.57
• 2.4.58
• 2.4.59
• 2.4.60
• 2.4.61
• 2.4.62
• 2.4.63
• 2.4.64
• 2.4.65
• 2.4.66
• 2.4.67
• 2.4.68
• 2.4.69
• 2.4.70
• 2.4.71
• 2.4.72
• 2.4.73
• 2.4.74
• 2.4.75
• 2.4.76
• 2.4.77
• 2.4.78

License

• open-source

Website

• Product: https://github.com/MISP/MISP/

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