{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-0436 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-0436 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-0436 is a medium-severity vulnerability in MongoDB Atlas Kubernetes Operator, published on 7 Nov 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-0436 and fix it if it is affected.\n\nWhat it is: CVE-2023-0436 is a medium-severity vulnerability in MongoDB Atlas Kubernetes Operator, published on 7 Nov 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-0436 in the wild and no public exploit code.\n\nAffected product: MongoDB Atlas Kubernetes Operator. 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-2023-0436/ (Markdown: https://insights.sbomify.com/CVE-2023-0436/index.md)","id":"CVE-2023-0436","markdown":"https://insights.sbomify.com/CVE-2023-0436/index.md","name":"CVE-2023-0436","record":{"aliases":[],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Kubernetes operator","requires_auth":"high_privilege","summary":"Attackers with access to debug logs can read sensitive credentials in MongoDB Atlas Kubernetes Operator when debug mode is enabled.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mongodb","cpe":[{"product":"atlas_kubernetes_operator","vendor":"mongodb"}],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"The affected versions of MongoDB Atlas Kubernetes Operator may print sensitive information like GCP service account keys and API integration secrets while DEBUG mode logging is enabled. This issue affects MongoDB Atlas Kubernetes Operator versions: 1.5.0, 1.6.0, 1.6.1, 1.7.0.\n\nPlease note that this is reported on an EOL version of the product, and users are advised to upgrade to the latest supported version.\nRequired Configuration: \n\nDEBUG logging is not enabled by default, and must be configured by the end-user. To check the log-level of the Operator, review the flags passed in your deployment configuration (eg.  https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27 https://github.com/mongodb/mongodb-atlas-kubernetes/blob/main/config/manager/manager.yaml#L27 )","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Secret logging may occur in debug mode of Atlas Operator","id":"CVE-2023-0436","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"MongoDB client C Driver may infinitely loop when validating certain BSON input data","id":"CVE-2023-0437"},"packages":[],"prev":{"headline":"Excessive Attack Surface in pyload/pyload","id":"CVE-2023-0435"},"products":["MongoDB Atlas Kubernetes Operator"],"published":"2023-11-07","related":[],"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-02","vendors":["MongoDB Inc"]},"summary":"Attackers with access to debug logs can read sensitive credentials in MongoDB Atlas Kubernetes Operator when debug mode is enabled.","url":"https://insights.sbomify.com/CVE-2023-0436/"}