VYPR
Unrated severityNVD Advisory· Published Jun 14, 2022· Updated Aug 4, 2024

CVE-2021-40650

CVE-2021-40650

Description

Connx 6.2.0.1269 issues a cookie without the Secure flag, exposing session data over unencrypted HTTP connections.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Connx 6.2.0.1269 issues a cookie without the Secure flag, exposing session data over unencrypted HTTP connections.

Vulnerability

In Connx version 6.2.0.1269 (20210623), the application sets a cookie (Set-Cookie: .ASPXANONYMOUS) without the Secure flag. The cookie is transmitted over HTTPS but the missing flag means it can also be sent over unencrypted HTTP connections, violating best practices for secure session handling. [1]

Exploitation

An attacker in a position to perform a man-in-the-middle attack on an unencrypted HTTP connection (e.g., on a compromised or open Wi-Fi network) can intercept the cookie. The cookie, HttpOnly but not Secure, would be transmitted over HTTP if the application does not enforce HTTPS redirects for all pages. No user interaction beyond the victim using the application over an untrusted network is required. [1]

Impact

A successful attacker can obtain the session cookie, allowing them to impersonate the victim and gain unauthorized access to the application's functionality and data under the victim's privileges. This leads to potential information disclosure and account takeover. [1]

Mitigation

The application must be configured to set the Secure flag on all cookies, ensuring they are only transmitted over HTTPS. As of the published reference, no fixed version is mentioned by the vendor. Administrators should enforce HTTPS-only communication and set the Secure flag on the cookie via application configuration or web server rules. [1]

AI Insight generated on May 27, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

1

News mentions

0

No linked articles in our index yet.