dbcve.org
En6200 Prime Quad 35 FirmwareOperating system · Tacitine

CVE-2022-40630

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 22.21.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
This vulnerability exists in Tacitine Firewall, all versions of EN6200-PRIME QUAD-35 and EN6200-PRIME QUAD-100 between 19.1.1 to 22.20.1 (inclusive), due to improper session management in the Tacitine Firewall web-based management interface. An unauthenticated remote attacker could exploit this vulnerability by sending a specially crafted http request on the targeted device. Successful exploitation of this vulnerability could allow an unauthenticated remote attacker to perform session fixation on the targeted device.

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

This is a session fixation vulnerability in Tacitine Firewall's web-based management interface (EN6200-PRIME devices versions 19.1.1 to 22.20.1). An unauthenticated remote attacker can send a specially crafted HTTP request to set or fix a session ID before a legitimate user authenticates, then hijack the user's authenticated session by using that same session ID.

MitigationImplement proper session ID regeneration upon successful authentication and invalidate any pre-authentication session IDs. Additionally, configure the application to reject client-supplied session identifiers and generate cryptographically random session IDs server-side.

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
En6200 Prime Quad 35 FirmwareOperating system
Affected:>= 19.1.1, < 22.21.2
En6200 Prime Quad 100 FirmwareOperating system
Affected:>= 19.1.1, < 22.21.2

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
High
Integrity
High
Availability
High

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

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. Identify device model
    Access the device console or web interface and look for the model identifier. On the EN6200-PRIME, the model is typically displayed in the web interface header or system status page.
    Affected if Device model is Tacitine En6200 Prime Quad 35 or En6200 Prime Quad 100
  2. Check firmware version
    In the web-based management interface, navigate to System > Status or System > Firmware to view the installed firmware version. Alternatively, use the CLI command 'show system info' or 'get firmware version'.
    Affected if Firmware version is greater than or equal to 19.1.1 and less than 22.21.2
  3. Verify web management interface is enabled
    Check the device configuration for web interface status. In the web UI, go to System > Administration > Access Settings or use CLI 'show webui status' to confirm the management interface is active.
    Affected if Web-based management interface is enabled and accessible on HTTP/HTTPS ports
  4. Test session ID behavior before authentication
    Using a browser or HTTP tool, attempt to access the login page while setting a custom session cookie (e.g., PHPSESSID=test123). Repeat the request after authentication to observe if the same session ID is retained.
    Affected if The same session ID provided before authentication persists after successful login (session is not regenerated)
  5. Check for session fixation protection
    Examine the HTTP response headers and cookies during the login process. Look for Set-Cookie headers that set session identifiers. Compare session IDs before and after authentication to see if they change.
    Affected if Session ID remains unchanged between pre-authentication and post-authentication requests

The environment is affected if the device is an EN6200-PRIME model running firmware between 19.1.1 and 22.20.1 with the web management interface enabled, and the session ID is not regenerated upon authentication.

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.

dbcve · scoped
Upgrade available Upgrade to 22.21.2 or later
Fixed in 22.21.2
Interim mitigation

Implement proper session ID regeneration upon successful authentication and invalidate any pre-authentication session IDs. Additionally, configure the application to reject client-supplied session identifiers and generate cryptographically random session IDs server-side.

Recommended fix High confidence

Firmware version 22.21.2 or later

  1. 1. Download the firmware version 22.21.2 or later from the official Tacitine/EN6200 vendor support portal
  2. 2. Access the EN6200 Prime device web-based management interface
  3. 3. Navigate to the Firmware Upgrade or System Maintenance section
  4. 4. Upload the downloaded firmware file (22.21.2 or later)
  5. 5. Confirm the upgrade and wait for the device to reboot
  6. 6. After reboot, verify the firmware version is 22.21.2 or higher in the device status or about section
Caveat Review release notes for any configuration or feature changes between your current version and 22.21.2; a backup of configuration is recommended before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in En6200 Prime Quad 35 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2022-40630 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