Lucene search
K

INFOR EAM 11.0 Build 201410 - Persistent Cross-Site Scripting via Comment Fields

🗓️ 17 May 2017 00:00:00Reported by YoroiType 
exploitdb
 exploitdb
🔗 www.exploit-db.com👁 55 Views

INFOR EAM 11.0 Build 201410 Persistent XSS via Comment Fields. Impact: Administrative Credential Thef

Related
Code
ReporterTitlePublishedViews
Family
0day.today
INFOR EAM 11.0 Build 201410 - Persistent Cross-Site Scripting via Comment Fields Vulnerability
17 May 201700:00
zdt
CNVD
INFOR EAM Cross-Site Scripting Attack Vulnerability
24 May 201700:00
cnvd
CVE
CVE-2017-7953
16 May 201710:00
cve
Cvelist
CVE-2017-7953
16 May 201710:00
cvelist
EUVD
EUVD-2017-16924
7 Oct 202500:30
euvd
exploitpack
INFOR EAM 11.0 Build 201410 - Persistent Cross-Site Scripting via Comment Fields
17 May 201700:00
exploitpack
NVD
CVE-2017-7953
16 May 201710:29
nvd
OSV
CVE-2017-7953
16 May 201710:29
osv
Packet Storm
INFOR EAM 11.0 Build 201410 Cross Site Scripting
15 May 201700:00
packetstorm
Prion
Design/Logic Flaw
16 May 201710:29
prion
Rows per page
Stored XSS in INFOR EAM V11.0 Build 201410 via comment fields
-------------------
Assigned CVE: CVE-2017-7953

Reproduction steps:
-------------------
1. Log in with your EAM account
2. Go to the jobs page
3. Click on a record and open its page
4. Go to "Comments" tab
4. Click the add new comment button
5. Insert a comment containing javascript code, e.g. <img src=fakesource onerror="alert(document.cookie)"> Fake comment here
6. Save, and after page reloading the XSS should trigger

Example:
-------------------
PoC Screenshot: https://www.dropbox.com/s/2b859x9go8v9f2l/xss.png?dl=0


Exploitability
-------------------
In EAM software user comments have read classification to every 
authenticated users. Any authenticated user could became a valid victim to 
the described attack by navigate (spontaneously or not) to the infected 
page. The comment visualization triggers injected javascript code.
On the other side any user able to write a comment could become a possible 
attacker by introducing javascript into the comment body.

Impact
-------------------
By reading browser cookies an attacker could ultimately grab administrative 
credentials having access to each available EAM action.
The vulnerability could ultimately allow an attacker to steal credential, 
leak sensitive data, trick user to download malware.

Disclosure timeline
-------------------

26.04.2017 Vulnerability reported to vendor
15.05.2017 Advisory published

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation