Ssl Network ExtenderApplication · Checkpoint

CVE-2021-30357

MEDIUM · 5.3 CVSS v3.1 Published 2021-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SSL Network Extender Client for Linux before build 800008302 reveals part of the contents of the configuration file supplied, which allows partially disclosing files to which the user did not have access.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SSL Network Extender Client for Linux versions prior to build 800008302 contain an information disclosure vulnerability that allows partial disclosure of configuration files to users who should not have access to them. This represents a file authorization bypass where the client improperly exposes sensitive configuration content.

MitigationUpgrade SSL Network Extender Client for Linux to build 800008302 or later to address the file disclosure vulnerability. In the meantime, restrict access to configuration files and monitor for unauthorized access attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ssl Network ExtenderApplication
Affected:= r80.10= r80.20= r80.30= r80.40= r81

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SSL Network Extender Client for Linux is installed
    Look for the client installation in common Linux paths such as /opt/sslnx, /usr/local/sslnx, or check for processes named 'sslnx' or 'swnnx' running on the system
    Affected if The client binary or related processes are found on the system
  2. Identify the installed version and build number
    Run 'sslnx --version' or check version information in the client installation directory, typically found in a version file or the client binary metadata
    Affected if The version matches r80.10, r80.20, r80.30, r80.40, or r81 with a build number lower than 800008302
  3. Locate configuration files used by the client
    Search for configuration directories such as ~/.sslnx, /etc/sslnx, or the client installation config folder - look for files like config.dat, client.conf, or similar configuration XML/JSON files
    Affected if Configuration files exist in the expected client directories
  4. Verify file permissions on configuration files
    Run 'ls -la' on the identified configuration directories and files to inspect read permissions for other users or groups
    Affected if Configuration files are readable by users who should not have access (permissions show world-readable or group-readable by unintended groups)
  5. Check for unauthorized access indicators in configuration file contents
    Examine the configuration files to determine if sensitive content such as credentials, server addresses, or internal network settings are exposed that should not be visible to all users
    Affected if Sensitive configuration content is present and accessible to unauthorized users

Users are affected if SSL Network Extender Client for Linux is installed with version r80.10 through r81 at a build prior to 800008302 and configuration files are accessible to unauthorized users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SSL Network Extender Client for Linux to build 800008302 or later to address the file disclosure vulnerability. In the meantime, restrict access to configuration files and monitor for unauthorized access attempts.

Fix this in Ssl Network Extender Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-30357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-30357 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data