CVE-2024-46937
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 · uneditedAn improper access control (IDOR) vulnerability in the /api-selfportal/get-info-token-properties endpoint in MFASOFT Secure Authentication Server (SAS) 1.8.x through 1.9.x before 1.9.040924 allows remote attackers gain access to user tokens without authentication. The is a brute-force attack on the serial parameter by number identifier: GA00001, GA00002, GA00003, etc.
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 confidenceThis is an IDOR (Insecure Direct Object Reference) vulnerability in MFASOFT Secure Authentication Server where the /api-selfportal/get-info-token-properties endpoint fails to verify user authorization before returning token information. Attackers can enumerate sequential serial numbers (GA00001, GA00002, etc.) to access sensitive token properties without any authentication, exposing user authentication tokens to unauthorized parties.
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>= 1.8.0, < 1.9.040924CVSS 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.
-
Identify the installed version of Mfasoft Secure Authentication ServerCheck the application version through the administrative console, installation directory metadata, or product about page. Common locations include the service management interface or version info file in the installation folder.Affected if The installed version is >= 1.8.0 and < 1.9.040924
-
Verify if the /api-selfportal/get-info-token-properties endpoint is accessibleAttempt to access the endpoint via HTTP/HTTPS request from an unauthenticated context, for example: GET /api-selfportal/get-info-token-properties?serial=GA00001Affected if The endpoint responds without requiring authentication (returns 200 OK instead of 401/403)
-
Confirm the self-portal module is enabledReview the server configuration or administrative settings to verify whether the self-portal API module is currently active/enabled.Affected if Self-portal module is enabled and the vulnerable endpoint is reachable
-
Test for IDOR via sequential token enumerationSend requests with incrementing serial number patterns (GA00001, GA00002, GA00003, etc.) to the endpoint without authentication and observe if sensitive token properties are returned.Affected if The endpoint returns token properties (such as user info, token secrets, or authentication data) for any serial number without requiring authorization
You are affected if the server runs version 1.8.0 through 1.9.040923, the self-portal is enabled, and the /api-selfportal/get-info-token-properties endpoint can be accessed without authentication to retrieve token information via serial number enumeration.
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.
dbcve · scoped1.9.040924
Implement proper authorization checks to verify the requesting user has legitimate access to the specific token being requested, and require valid authentication for the endpoint. Consider rate-limiting or CAPTCHA to impede brute-force enumeration attempts.
1.9.040924 or later
- Upgrade MFASOFT Secure Authentication Server to version 1.9.040924 or later
- After upgrading, verify that the /api-selfportal/get-info-token-properties endpoint now properly enforces authentication
- Confirm that brute-force attacks on the serial parameter (GA00001, GA00002, etc.) are no longer successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46937 — 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-2024-46937 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