{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10732 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10732 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10732 is a medium-severity vulnerability in n/a, published on 28 May 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-10732 and fix it if it is affected.\n\nWhat it is: CVE-2018-10732 is a medium-severity vulnerability in n/a, published on 28 May 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-10732 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-10732/ (Markdown: https://insights.sbomify.com/CVE-2018-10732/index.md)","id":"CVE-2018-10732","markdown":"https://insights.sbomify.com/CVE-2018-10732/index.md","name":"CVE-2018-10732","record":{"aliases":["GHSA-v299-6q62-275r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Dataiku DSS","requires_auth":"none","summary":"Remote attackers can determine valid usernames via profile picture visibility in the REST API, enabling user enumeration.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"data_science_studio","vendor":"dataiku"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"The REST API in Dataiku DSS before 4.2.3 allows remote attackers to obtain sensitive information (i.e., determine if a username is valid) because of profile pictures visibility.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-05-07","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-05-07T09:07:58Z","kind":"github_poc","ref":"https://github.com/alt3kx/CVE-2018-10732","stars":0,"title":"Dataiku REST-API by default the software, allows anonymous access to functionality that allows an attacker to know valid users."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2018-10732","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-10733"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-10731"},"products":["n/a"],"published":"2018-05-28","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2023-51717","kev_date_added":null,"published":"2024-01-09"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2020-8817","kev_date_added":null,"published":"2020-09-14"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2023-24045","kev_date_added":null,"published":"2023-03-01"},{"cvss_score":5.4,"headline":"Missing authorization in n/a","id":"CVE-2021-27225","kev_date_added":null,"published":"2021-03-01"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can determine valid usernames via profile picture visibility in the REST API, enabling user enumeration.","url":"https://insights.sbomify.com/CVE-2018-10732/"}