Northstar Club ManagementApplication · Globalnorthstar

CVE-2021-29394

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Account Hijacking in /northstar/Admin/changePassword.jsp in Northstar Technologies Inc NorthStar Club Management 6.3 allows remote authenticated users to change the password of any targeted user accounts via lack of proper authorization in the user-controlled "userID" parameter of the HTTP POST request.

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

The changePassword.jsp endpoint in NorthStar Club Management 6.3 lacks server-side authorization validation on the userID parameter. Any authenticated user can craft a POST request with an arbitrary userID to reset any other user's password, enabling complete account takeover of targeted accounts.

MitigationImplement server-side authorization checks to verify the requesting user has permission to modify the target user's password, typically by validating the userID matches the authenticated session or enforcing role-based access controls.

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
Northstar Club ManagementApplication
Affected:= 6.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 NorthStar Club Management installation
    Identify if the NorthStar Club Management application is installed and determine its version by checking the application banner, about page, or software inventory
    Affected if The installed version is exactly 6.3
  2. Locate changePassword.jsp endpoint
    Search the web server for the changePassword.jsp file, typically found in the web application's root or admin directory
    Affected if The changePassword.jsp endpoint exists and is accessible to authenticated users
  3. Verify endpoint accepts userID parameter
    Inspect the HTTP requests and parameters accepted by changePassword.jsp to confirm it accepts a userID parameter for password reset operations
    Affected if The endpoint accepts a userID parameter in the POST request for password modification
  4. Test authorization bypass
    As an authenticated user, submit a password change POST request with an arbitrary userID different from the authenticated session's userID
    Affected if The password reset completes successfully for a user other than the one in the current authenticated session, indicating missing server-side authorization validation

A user is affected if NorthStar Club Management version 6.3 is running and the changePassword.jsp endpoint allows password changes for arbitrary userIDs without verifying the requesting user has permission to modify that specific user's password.

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

Implement server-side authorization checks to verify the requesting user has permission to modify the target user's password, typically by validating the userID matches the authenticated session or enforcing role-based access controls.

Fix this in Northstar Club Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29394 — 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-29394 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