Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/minio/minio: CVE-2021-21362 #2322

Closed
tatianab opened this issue Nov 8, 2023 · 1 comment
Closed
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process

Comments

@tatianab
Copy link
Contributor

tatianab commented Nov 8, 2023

CVE-2021-21362 references github.com/minio/minio, which may be a Go module.

Description:
MinIO is an open-source high performance object storage service and it is API compatible with Amazon S3 cloud storage service. In MinIO before version RELEASE.2021-03-04T00-53-13Z it is possible to bypass a readOnly policy by creating a temporary 'mc share upload' URL. Everyone is impacted who uses MinIO multi-users. This is fixed in version RELEASE.2021-03-04T00-53-13Z. As a workaround, one can disable uploads with Content-Type: multipart/form-data as mentioned in the S3 API RESTObjectPOST docs by using a proxy in front of MinIO.

References:

Cross references:

See doc/triage.md for instructions on how to triage this report.

modules:
    - module: github.com/minio/minio
      vulnerable_at: 0.0.0-20231108174705-15137d032704
      packages:
        - package: minio
cves:
    - CVE-2021-21362
references:
    - advisory: https://github.com/minio/minio/security/advisories/GHSA-hq5j-6r98-9m8v
    - fix: https://github.com/minio/minio/pull/11682
    - fix: https://github.com/minio/minio/commit/039f59b552319fcc2f83631bb421a7d4b82bc482
    - web: https://github.com/minio/minio/releases/tag/RELEASE.2021-03-04T00-53-13Z

@tatianab tatianab added the excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process label Nov 8, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/540721 mentions this issue: data/excluded: batch add 135 excluded reports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: LEGACY_FALSE_POSITIVE (DO NOT USE) Vulnerability marked as false positive before we introduced the triage process
Projects
None yet
Development

No branches or pull requests

2 participants