Security readout for executives and security teams
Plain-English summary
MinIO before RELEASE.2023-03-20T20-16-18Z can let a logged-in attacker write objects into buckets they should not control. The attacker needs broad S3-style permission and Console API access, so exposure depends heavily on account policy and configuration. CISA KEV listing raises urgency because exploitation is known.
Executive priority
Prioritize remediation for internet-facing or shared MinIO deployments first. KEV status means regulators and attackers may both focus on this issue. Upgrade is the clearest control; policy review should follow to reduce damage from compromised low-privilege or over-permissioned accounts.
Technical view
The flaw is a CWE-269 privilege escalation in MinIO PostPolicyBucket processing. Crafted requests can bypass metadata bucket-name checks and place an object into any bucket. Sources state exploitation requires credentials with arn:aws:s3:::* permission plus enabled Console API access. Fixed in RELEASE.2023-03-20T20-16-18Z.
Likely exposure
Organizations running MinIO releases before RELEASE.2023-03-20T20-16-18Z on Linux or macOS are potentially exposed, especially where users or service accounts have broad arn:aws:s3:::* permissions and Console API access is enabled.
Exploitation context
CISA lists CVE-2023-28434 in the Known Exploited Vulnerabilities catalog, so treat it as known exploited. The provided sources do not describe specific campaigns, public exploit maturity, or attacker tooling. The required credential and Console API conditions limit exposure but do not remove business risk.
Researcher notes
Key conditions are important: this is not described as unauthenticated. The advisory says credentials with arn:aws:s3:::* and Console API access are required. Validate exposure through configuration, policy review, version checks, and log analysis rather than offensive reproduction.
Mitigation direction
- Upgrade MinIO to RELEASE.2023-03-20T20-16-18Z or later.
- Apply the MinIO advisory workaround if immediate upgrade is not possible.
- Review and reduce accounts with arn:aws:s3:::* permissions.
- Restrict Console API access to trusted administrative paths only.
- Monitor MinIO and CISA guidance for any updated remediation direction.
Validation and detection
- Inventory all MinIO deployments and confirm exact release versions.
- Identify accounts or service users with arn:aws:s3:::* permission.
- Confirm whether Console API access is enabled on affected deployments.
- Review object-write logs for unexpected bucket targets.
- Verify patched deployments no longer run vulnerable versions.
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.
CWE-269: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-28434 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
- 8.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
CISA KEV status
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.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/minio/minio/security/advisories/GHSA-2pxw-r47w-4p8cCVE reference · x_refsource_CONFIRM
- https://github.com/minio/minio/pull/16849CVE reference · x_refsource_MISC
- https://github.com/minio/minio/commit/67f4ba154a27a1b06e48bfabda38355a010dfca5CVE reference · x_refsource_MISC
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-28434CVE reference · government-resource
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.
Improper Privilege Management
Improper Privilege Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.