LISTSERV 17 Insecure Direct Object Reference ≈ Packet Storm

LISTSERV 17 Insecure Direct Object Reference ≈ Packet Storm

Home[1] Files[2] News[3] &[SERVICES_TAB] Contact[4] Add New[5]

LISTSERV 17 Insecure Direct Object Reference[6]
Authored by Shaunt D[7]

LISTSERV version 17 suffers from an insecure direct object reference vulnerability that allows illicit access to a target's profile.

advisories | CVE-2022-40319[8]
SHA-256 | 85ee07e1189f45c5c9a0a938efe4b03286c683eb59f7286a1f2c39fde88bf563

Change Mirror[12] Download[13]

        # Exploit Title: LISTSERV 17 - Insecure Direct Object Reference (IDOR)
# Exploit Author: Shaunt D
# Vendor Homepage:
# Version: 17
# Tested on: Windows Server 2019
# CVE : CVE-2022-40319
# Steps to replicate
1. Create two accounts on your LISTSERV 17 installation, logging into each one in a different browser or container.
2. Intercept your attacking profile's browser traffic using Burp.
3. When logging in, you'll be taken to a URL with your email address in the Y parameter (i.e.[session-id]&Y=[email-address]).
4. Click on your email address on the top right and select "Edit profile".
5. In Burp, change the email address in the URL's Y parameter to the email address of your victim account.
4. Next, the "WALOGIN" cookie value will be an ASCII encoded version of your email address. Using Burp Decoder, ASCII encode your victim's email address and replace the "WALOGIN" cookie value with that.5. Submit this request. You should now be accessing/editing the victim's profile. You can make modifications and access any information in this profile as long as you replace those two values in Burp for each request.

Login[14] or Register[15] to add favorites

File Archive:

January 2023

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa

File Tags

File Archives


packet storm

© 2022 Packet Storm. All rights reserved.

Hosting By

Pensée du jour :

Ce que l'homme a fait ,

l'homme peut le défaire.


"No secure path in the world"