Pulse Connect Secure
Approved changes feed: RSS · Atom
cpe:2.3:a:juniper:pulse_connect_secure:8.0:*:*:*:*:*:*:*
part: a version: 8.0 update: *
| Vendor | Juniper (e5b3b18f-e0e0-511d-8fa5-6b210c732f6e) |
|---|---|
| Product | Pulse Connect Secure (867e3dea-21fa-579b-b885-361940eac498) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2015-7323 |
vulnerable | 2026-06-08 05:07:00.432809 |
Details available
The Secure Meeting (Pulse Collaboration) in Pulse Connect Secure (formerly Juniper Junos Pulse) before 7.1R22.1, 7.4, 8.0 before 8.0R11, and 8.1 before 8.1R3 allows remote authenticated users to bypass intended access restrictions and log into arbitrary meetings by leveraging a meeting id and meetingAppSun.jar.
Published: 2015-10-05T15:00:00.000Z
Updated: 2024-08-06T07:43:46.118Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-7322 |
vulnerable | 2026-06-08 05:07:00.431799 |
Details available
The Secure Meeting (Pulse Collaboration) in Pulse Connect Secure (formerly Juniper Junos Pulse) before 7.1R22.1, 7.4, 8.0 before 8.0R11, and 8.1 before 8.1R3 provides different messages for attempts to join a meeting depending on the status of the meeting, which allows remote attackers to enumerate valid meeting ids via a series of requests.
Published: 2015-10-05T15:00:00.000Z
Updated: 2024-08-06T07:43:46.341Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-5369 |
vulnerable | 2026-06-08 05:06:49.874047 |
Details available
Pulse Connect Secure (aka PCS and formerly Juniper PCS) PSC6000, PCS6500, and MAG PSC360 8.1 before 8.1r5, 8.0 before 8.0r13, 7.4 before 7.4r13.5, and 7.1 before 7.1r22.2 and PPS 5.1 before 5.1R5 and 5.0 before 5.0R13, when Hardware Acceleration is enabled, does not properly validate the Finished TLS handshake message, which makes it easier for remote attackers to conduct man-in-the-middle attacks via a crafted Finished message.
Published: 2015-08-11T14:00:00.000Z
Updated: 2024-08-06T06:41:09.315Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.