CWE
200
Advisory Published
Updated

CVE-2020-8216: Infoleak

First published: Thu Jul 30 2020(Updated: )

An information disclosure vulnerability in meeting of Pulse Connect Secure <9.1R8 allowed an authenticated end-users to find meeting details, if they know the Meeting ID.

Credit: support@hackerone.com support@hackerone.com

Affected SoftwareAffected VersionHow to fix
Pulsesecure Pulse Connect Secure<=9.0
Pulsesecure Pulse Connect Secure=9.1
Pulsesecure Pulse Connect Secure=9.1-r1
Pulsesecure Pulse Connect Secure=9.1-r2
Pulsesecure Pulse Connect Secure=9.1-r3
Pulsesecure Pulse Connect Secure=9.1-r4
Pulsesecure Pulse Connect Secure=9.1-r4.1
Pulsesecure Pulse Connect Secure=9.1-r4.2
Pulsesecure Pulse Connect Secure=9.1-r4.3
Pulsesecure Pulse Connect Secure=9.1-r5
Pulsesecure Pulse Connect Secure=9.1-r6
Pulsesecure Pulse Connect Secure=9.1-r7
Pulsesecure Pulse Policy Secure<=9.0
Pulsesecure Pulse Policy Secure=9.1
Pulsesecure Pulse Policy Secure=9.1-r1
Pulsesecure Pulse Policy Secure=9.1-r2
Pulsesecure Pulse Policy Secure=9.1-r3
Pulsesecure Pulse Policy Secure=9.1-r3.1
Pulsesecure Pulse Policy Secure=9.1-r4
Pulsesecure Pulse Policy Secure=9.1-r4.1
Pulsesecure Pulse Policy Secure=9.1-r4.2
Pulsesecure Pulse Policy Secure=9.1-r5
Pulsesecure Pulse Policy Secure=9.1-r6
Pulsesecure Pulse Policy Secure=9.1-r7
Ivanti Connect Secure=9.1
Ivanti Connect Secure=9.1-r1
Ivanti Connect Secure=9.1-r2
Ivanti Connect Secure=9.1-r3
Ivanti Connect Secure=9.1-r4
Ivanti Connect Secure=9.1-r4.1
Ivanti Connect Secure=9.1-r4.2
Ivanti Connect Secure=9.1-r4.3
Ivanti Connect Secure=9.1-r5
Ivanti Connect Secure=9.1-r6
Ivanti Connect Secure=9.1-r7
Ivanti Policy Secure=9.1
Ivanti Policy Secure=9.1-r1
Ivanti Policy Secure=9.1-r2
Ivanti Policy Secure=9.1-r3
Ivanti Policy Secure=9.1-r3.1
Ivanti Policy Secure=9.1-r4
Ivanti Policy Secure=9.1-r4.1
Ivanti Policy Secure=9.1-r4.2
Ivanti Policy Secure=9.1-r5
Ivanti Policy Secure=9.1-r6
Ivanti Policy Secure=9.1-r7

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2020-8216?

    The severity of CVE-2020-8216 is medium with a CVSS score of 4.3.

  • What is the vulnerability description of CVE-2020-8216?

    CVE-2020-8216 is an information disclosure vulnerability in meeting of Pulse Connect Secure <9.1R8 which allows authenticated end-users to find meeting details using the Meeting ID.

  • What software versions are affected by CVE-2020-8216?

    The following software versions are affected by CVE-2020-8216: Pulse Connect Secure 9.0, Pulse Connect Secure 9.1 (up to and including 9.1-r7), Pulse Policy Secure 9.0, Pulse Policy Secure 9.1 (up to and including 9.1-r7).

  • How can I fix CVE-2020-8216?

    To fix CVE-2020-8216, upgrade to Pulse Connect Secure version 9.1R8 or later.

  • Where can I find more information about CVE-2020-8216?

    You can find more information about CVE-2020-8216 [here](https://kb.pulsesecure.net/articles/Pulse_Security_Advisories/SA44516).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203