{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-9129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-9129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-9129 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 28 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-9129 and fix it if it is affected.\n\nWhat it is: CVE-2016-9129 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 28 Mar 2017. 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-2016-9129 in the wild and no public exploit code.\n\nAffected product: Revive-Adserver Revive Adserver. 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-2016-9129/ (Markdown: https://insights.sbomify.com/CVE-2016-9129/index.md)","id":"CVE-2016-9129","markdown":"https://insights.sbomify.com/CVE-2016-9129/index.md","name":"CVE-2016-9129","record":{"aliases":["GHSA-43m8-rg5f-9pr8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ad server software","requires_auth":"none","summary":"Attackers can determine if email addresses are registered by analyzing password recovery messages, exposing user account existence.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"revive_adserver","vendor":"revive-adserver"}],"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"},{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Revive Adserver before 3.2.3 suffers from Information Exposure Through Discrepancy. It is possible to check whether or not an email address was associated to one or more user accounts on a target Revive Adserver instance by examining the message printed by the password recovery system. Such information cannot however be used directly to log in to the system, which requires a username.","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":"Information disclosure in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"revive-adserver:revive_adserver","products":["revive-adserver:revive_adserver"],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9130"},"packages":[],"prev":{"headline":"Cross-site scripting in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9128"},"products":["Revive Adserver All versions before 3.2.3"],"published":"2017-03-28","related":[{"cvss_score":9.8,"headline":"Security feature bypass in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9124","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":9.8,"headline":"Auth bypass in Revive Adserver All versions before 3.2.3","id":"CVE-2016-9125","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2017-5830","kev_date_added":null,"published":"2017-03-03"},{"cvss_score":9,"headline":"Other in Revive Adserver All versions before 3.2.5 and 4.0.0","id":"CVE-2016-9470","kev_date_added":null,"published":"2017-03-28"},{"cvss_score":8.8,"headline":"Code injection in Adserver","id":"CVE-2026-50741","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":8.8,"headline":"Missing authorization in Revive Adserver","id":"CVE-2025-48986","kev_date_added":null,"published":"2025-11-20"},{"cvss_score":8.8,"headline":"SQL injection in Revive Adserver","id":"CVE-2025-52664","kev_date_added":null,"published":"2025-10-30"}],"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-06","vendors":["n/a"]},"summary":"Attackers can determine if email addresses are registered by analyzing password recovery messages, exposing user account existence.","url":"https://insights.sbomify.com/CVE-2016-9129/"}