CVE-2023-30059
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 insecure direct object reference in MK-Auth 23.01K4.9 allows attackers to access and send support calls for other users via manipulation of the chamado parameter through a crafted GET 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 · moderate confidenceMK-Auth 23.01K4.9 contains an Insecure Direct Object Reference (IDOR) vulnerability in the support call functionality. Attackers can manipulate the 'chamado' parameter in GET requests to access and send support tickets belonging to other users, bypassing proper authorization controls.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 MK-Auth installationLocate the MK-Auth web application directory or check running services on the host. Common locations may include /var/www/, /opt/, or the web server document root. Look for files or directories named 'mk-auth' or similar.Affected if MK-Auth software is present on the system
-
Determine installed MK-Auth versionCheck version information in the application - typically found in an about page, config file, or the main index file. Compare the installed version against 23.01K4.9.Affected if The installed version matches or falls within the range of 23.01K4.9 (if version ranges beyond this single version are known to be affected)
-
Verify support call module is enabledAccess the MK-Auth administrative interface and check if the support ticket or 'chamado' functionality is present and enabled. This may appear as a support, tickets, or chamado menu item.Affected if The support call (chamado) module is accessible and enabled in the application
-
Inspect support call request parametersIf you have access to the application, navigate to the support call feature and examine GET requests. Look for a 'chamado' parameter in the URL used to access or view specific tickets.Affected if The application uses a 'chamado' parameter to reference support tickets in GET requests
-
Test for IDOR vulnerabilityIf you have multiple test accounts, access a support ticket with one account, then modify the 'chamado' parameter value in the GET request to reference a ticket ID belonging to a different user. Verify if unauthorized access is granted without proper authorization.Affected if Changing the 'chamado' parameter value allows access to support tickets belonging to other users
A defender is affected if MK-Auth version 23.01K4.9 is installed with the support call module enabled and the 'chamado' parameter in GET requests permits unauthorized access to other users' tickets.
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 dataImplement proper authorization checks to verify the authenticated user owns or has permission to access the specific support call before returning or modifying any data. Use session-based validation rather than relying on user-controllable object references.
- 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-2023-30059 — 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-2023-30059 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