{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1000538 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-1000538 is a high-severity denial of service vulnerability in n/a, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-1000538 and fix it if it is affected.\n\nWhat it is: CVE-2018-1000538 is a high-severity denial of service vulnerability in n/a, published on 26 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-1000538 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-1000538/ (Markdown: https://insights.sbomify.com/CVE-2018-1000538/index.md)","id":"CVE-2018-1000538","markdown":"https://insights.sbomify.com/CVE-2018-1000538/index.md","name":"CVE-2018-1000538","record":{"aliases":["MINI-h9fj-pm3v-whpp","MINI-vc98-jcw3-4wgp"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Minio S3 server","requires_auth":"none","summary":"Attackers can cause denial of service in Minio S3 server by sending large signed request bodies, exhausting memory resources.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"minio","vendor":"minio"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-774","name":"Allocation of File Descriptors or Handles Without Limits or Throttling"}],"description":"Minio Inc. Minio S3 server version prior to RELEASE.2018-05-16T23-35-33Z contains a Allocation of Memory Without Limits or Throttling (similar to CWE-774) vulnerability in write-to-RAM that can result in Denial of Service. This attack appear to be exploitable via Sending V4-(pre)signed requests with large bodies . This vulnerability appears to have been fixed in after commit 9c8b7306f55f2c8c0a5c7cea9a8db9d34be8faa7.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Denial of service in n/a","id":"CVE-2018-1000538","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Json-jwt did not verify the cryptographic signature for data","id":"CVE-2018-1000539"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-1000537"},"products":["n/a"],"published":"2018-06-26","related":[{"cvss_score":8.8,"headline":"MinIO Security Feature Bypass","id":"CVE-2023-28434","kev_date_added":"2023-09-19","published":"2023-03-22"},{"cvss_score":7.5,"headline":"MinIO Information Disclosure","id":"CVE-2023-28432","kev_date_added":"2023-04-21","published":"2023-03-22"},{"cvss_score":9.3,"headline":"Authentication bypass MinIO Admin API","id":"CVE-2020-11012","kev_date_added":null,"published":"2020-04-23"},{"cvss_score":9.2,"headline":"MinIO: JWT Algorithm Confusion in OIDC Authentication","id":"CVE-2026-33322","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":9.1,"headline":"MinIO: LDAP login brute-force via user enumeration and missing rate limit","id":"CVE-2026-33419","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.8,"headline":"MinIO has an Unauthenticated Object Write via Missing Signature Verification in Unsigned-Trailer Uploads","id":"CVE-2026-40344","kev_date_added":null,"published":"2026-04-22"},{"cvss_score":8.8,"headline":"MinIO has an Unauthenticated Object Write via Query-String Credential Signature Bypass in Unsigned-Trailer Uploads","id":"CVE-2026-41145","kev_date_added":null,"published":"2026-04-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can cause denial of service in Minio S3 server by sending large signed request bodies, exhausting memory resources.","url":"https://insights.sbomify.com/CVE-2018-1000538/"}