CVE-2023-30059: An insecure direct object reference in MK-Auth 23.01K4.9 allows attackers to access and send support calls...
An 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.
Security readout for executives and security teams
Plain-English summary
MK-Auth 23.01K4.9 has an authorization flaw that can let a logged-in attacker view or send support calls belonging to other users. The issue is not described as unauthenticated or actively exploited. Business urgency is moderate: confidentiality and integrity of support interactions may be affected, but availability impact is not indicated.
Executive priority
Treat this as a moderate-priority access-control issue. Prioritize if MK-Auth handles sensitive customer support content or if many low-trust users can log in. No active exploitation evidence is provided in the source bundle.
Technical view
CVE-2023-30059 is a CWE-639 insecure direct object reference in MK-Auth 23.01K4.9 involving the support-call object referenced by the chamado parameter. The CVSS 3.1 score is 5.4, with network access, low attack complexity, low privileges required, no user interaction, and low confidentiality and integrity impact.
Likely exposure
Exposure is most likely limited to organizations running MK-Auth 23.01K4.9 where untrusted or lower-privileged authenticated users can access the support-call functionality. The CVE metadata does not provide vendor CPEs or broader affected version ranges.
Exploitation context
The source bundle does not show CISA KEV listing or another cited source confirming active exploitation. The vulnerability is plausible to abuse remotely after login because the CVSS vector indicates network access, low privileges, and no user interaction.
Researcher notes
Evidence is limited. The CVE identifies MK-Auth 23.01K4.9 and CWE-639, but affected CPEs, vendor advisory, patch status, and exact remediation are not included. Avoid assuming wider version impact until vendor or CVE data confirms it.
Mitigation direction
Check MK-Auth vendor guidance for a fixed version or official workaround.
Restrict support-call access to trusted authenticated roles where operationally possible.
Review authorization checks on support-call read and send actions.
Monitor support-call access for cross-account or unusual object access patterns.
Limit external exposure of the MK-Auth interface where feasible.
Validation and detection
Inventory MK-Auth deployments and confirm whether version 23.01K4.9 is present.
Identify which authenticated user roles can access support-call features.
Review application logs for unusual support-call access across user accounts.
Validate authorization behavior in an approved test environment without using production data.
Track the CVE record and referenced repository for remediation updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.