exploit the possibilities
Home Files News &[SERVICES_TAB]About Contact Add New

Verint Impact 360 15.1 Cross Site Request Forgery

Verint Impact 360 15.1 Cross Site Request Forgery
Posted Jul 14, 2020
Authored by Ryan Delaney

Verint Impact 360 version 15.1 suffers from a cross site request forgery vulnerability.

tags | exploit, csrf
advisories | CVE-2019-12784
SHA-256 | 8c1ec5a43ee4412962b923d2c0abe80de645b915f6144f18aa147efd40de3464

Verint Impact 360 15.1 Cross Site Request Forgery

Change Mirror Download
<!--
# Exploit Title: Verint Impact 360 login CSRF
# Date: 7-13-2020
# Exploit Author: Ryan Delaney
# Author Contact: ryan.delaney@owasp.org
# Author LinkedIn: https://www.linkedin.com/in/infosecrd/
# Vendor Homepage: https://www.verint.com/
# Software Link:
https://www.verint.com/engagement/our-offerings/solutions/workforce-optimization/
# Version: Impact 360 v15.1
# Tested on: Impact 360 v15.1
# CVE: CVE-2019-12784

1. Description

An issue was discovered in Verint Impact 360 15.1. At wfo/control/signin,
the login form can accept POST submissions from external sources. This may
allow attackers to compromise credentials via bruteforce login attempts
through users in the target environment running JS provided by the attacker
(e.g. malvertising) via XHR, and be notified of a successful login attempt
via a unique callback from CVE-2019-12783 to an attacker-owned web server,
even if the site is not accessible to the attacker due to firewall rules or
network configuration.

2. Mitigation

Create firewall rules to drop traffic going to the Impact 360 system with
an external referrer.
Request a patch from Verint. Verint has not patched this vulnerability to
my knowledge, despite having been made aware of it over a year ago.

3. PoC

Withheld due to possible legal threat.

4. Timeline

Discovered: 6-7-2019
CVE assigned: 6-10-2019
First contact: 6-14-2019 (no response)
Follow-up 1: 6-25-2019
Reply received: 7-9-2019 (stating that the responsible disclosure line
was for the community edition and report would be forwarded to enterprise)
Follow-up 2: 7-16-2019
Reply received: 7-19-2019 (cc'ing another individual and asking them to
follow up with me)
Follow-up 3: 8-30-2019 (no response)
Follow-up 4: 9-4-2019 (no response)
Follow-up 5: 9-11-2019 (no response)
Follow-up 6: 1-6-2020 (notification of intent to disclose in 90 days, no
response)
Follow-up 7: 3-5-2020 (notification of intent to disclose in 30 days)
Reply received: 3-6-2020 (requesting addition delay for disclosure)
Follow-up 8: 3-27-2020 (no response)
Follow-up 9: 5-18-2020 (no response)
Follow-up 10: 6-25-2020 (notification of intent to disclose, requesting
confirmation that legal action will not be pursued, no response)
Published: 7-13-2020 (260 business days after initial report)

-->


Login or Register to add favorites

File Archive:

March 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Mar 1st
    16 Files
  • 2
    Mar 2nd
    0 Files
  • 3
    Mar 3rd
    0 Files
  • 4
    Mar 4th
    32 Files
  • 5
    Mar 5th
    28 Files
  • 6
    Mar 6th
    42 Files
  • 7
    Mar 7th
    17 Files
  • 8
    Mar 8th
    13 Files
  • 9
    Mar 9th
    0 Files
  • 10
    Mar 10th
    0 Files
  • 11
    Mar 11th
    15 Files
  • 12
    Mar 12th
    19 Files
  • 13
    Mar 13th
    21 Files
  • 14
    Mar 14th
    38 Files
  • 15
    Mar 15th
    15 Files
  • 16
    Mar 16th
    0 Files
  • 17
    Mar 17th
    0 Files
  • 18
    Mar 18th
    10 Files
  • 19
    Mar 19th
    32 Files
  • 20
    Mar 20th
    46 Files
  • 21
    Mar 21st
    16 Files
  • 22
    Mar 22nd
    13 Files
  • 23
    Mar 23rd
    0 Files
  • 24
    Mar 24th
    0 Files
  • 25
    Mar 25th
    12 Files
  • 26
    Mar 26th
    31 Files
  • 27
    Mar 27th
    19 Files
  • 28
    Mar 28th
    42 Files
  • 29
    Mar 29th
    0 Files
  • 30
    Mar 30th
    0 Files
  • 31
    Mar 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close