Security readout for executives and security teams
Plain-English summary
Kyma versions before 1.24 allowed authenticated users to supply chosen headers in a way that could raise their privileges. This is a business concern where Kyma supports production platform operations, because a valid low-privilege account could gain more control than intended.
Executive priority
Treat as high priority for affected Kyma environments, especially production clusters. The key risk is authenticated privilege escalation, not broad internet-scale exploitation based on current evidence.
Technical view
The issue is insufficient input validation in SAP Kyma before 1.24. CVSS 7.6 indicates network access, low attack complexity, required low privileges, no user interaction, high integrity impact, and limited confidentiality and availability impact.
Likely exposure
Exposure is limited to organizations running SAP Kyma versions earlier than 1.24. Risk is highest where many users or service accounts have authenticated access to Kyma-managed components.
Exploitation context
The supplied sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires authenticated access. Public detail is limited, so do not assume unauthenticated compromise or a specific exploit path from the available evidence.
Researcher notes
Available public detail is sparse. The core signal is authenticated header control causing privilege escalation in Kyma <1.24, with CVSS vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L. Validate exposure by version and authentication boundaries.
Mitigation direction
- Upgrade Kyma deployments below 1.24 to version 1.24 or later.
- Review the Kyma GitHub advisory for vendor-specific remediation details.
- Limit Kyma access to trusted users and tightly scoped service accounts.
- Monitor privileged Kyma actions from low-privilege accounts until remediated.
Validation and detection
- Inventory all Kyma deployments and record their running versions.
- Flag any Kyma instance running a version earlier than 1.24.
- Review recent Kyma audit logs for unexpected privilege changes.
- Confirm upgraded deployments report Kyma version 1.24 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2021-33708 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.6 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L2.84.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.0 score
7.6HighVector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/kyma-project/kyma/security/advisories/GHSA-f2jp-5gj4-q9c9CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.