CVE-2021-29397
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 · uneditedCleartext Transmission of Sensitive Information in /northstar/Admin/login.jsp in Northstar Technologies Inc NorthStar Club Management 6.3 allows remote local user to intercept users credentials transmitted in cleartext over HTTP.
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 confidenceThe login.jsp page in NorthStar Club Management 6.3 transmits user credentials in cleartext over HTTP instead of using encrypted HTTPS, allowing a remote local attacker on the same network to intercept authentication credentials.
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= 6.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify if HTTP access is enabled on the serverAttempt to access the application over HTTP using a web browser or curl command: http://[server-hostname]/login.jsp or http://[server-hostname]:8080/login.jsp (adjust port as needed). If the page loads, HTTP is enabled.Affected if The login.jsp page is accessible over HTTP (non-encrypted connection)
-
Check if HTTPS is configured and accessibleAttempt to access the same login page over HTTPS: https://[server-hostname]/login.jsp or https://[server-hostname]:8443/login.jsp. If this fails or returns an error, HTTPS may not be configured.Affected if HTTPS is not available or not configured for the login page
-
Inspect the login form action URLView the source of the login.jsp page (accessible via HTTP) and examine the <form> tag's action attribute. Check if the action URL begins with http:// instead of https://.Affected if The login form action URL uses http:// instead of https://, indicating credentials will be sent unencrypted
-
Capture network traffic to verify cleartext transmissionUse a network packet capture tool (such as Wireshark or tcpdump) on the client or network segment while submitting login credentials over HTTP. Verify that the HTTP POST request contains readable username and password fields.Affected if Login credentials are transmitted in cleartext within unencrypted HTTP packets
A user is affected if the login.jsp page is accessible over HTTP and accepts/transmits authentication credentials without TLS encryption.
Generated from the published advisory. Verify against your own configuration.
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 dataEnable HTTPS on the server and configure the application to enforce SSL/TLS for all authentication pages, redirecting HTTP to HTTPS to ensure credentials are always encrypted in transit.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2021-29397 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-29397 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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