{"api_version":"1","generated_at":"2026-07-23T01:52:09+00:00","cve":"CVE-2016-9129","urls":{"html":"https://cve.report/CVE-2016-9129","api":"https://cve.report/api/cve/CVE-2016-9129.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2016-9129","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2016-9129"},"summary":{"title":"CVE-2016-9129","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.","state":"PUBLISHED","assigner":"hackerone","published_at":"2017-03-28 02:59:00","updated_at":"2025-04-20 01:37:25"},"problem_types":["CWE-203","CWE-200","CWE-203 Information Exposure Through Discrepancy (CWE-203)"],"metrics":[{"version":"3.0","source":"nvd@nist.gov","type":"Primary","score":"5.3","severity":"MEDIUM","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","data":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"NONE","availabilityImpact":"NONE"}},{"version":"2.0","source":"nvd@nist.gov","type":"Primary","score":"5","severity":"","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","data":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:N/A:N","baseScore":5,"accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE"}}],"references":[{"url":"https://www.revive-adserver.com/security/revive-sa-2016-001/","name":"https://www.revive-adserver.com/security/revive-sa-2016-001/","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Patch","Vendor Advisory"],"title":"Revive Adserver Security Advisory SA-2016-001 | Revive Adserver","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5","name":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Issue Tracking","Patch","Third Party Advisory"],"title":"Fix h1 report 98612 · revive-adserver/revive-adserver@38223a8 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://hackerone.com/reports/98612","name":"https://hackerone.com/reports/98612","refsource":"af854a3a-2127-422b-91ae-364da2661108","tags":["Permissions Required"],"title":"HackerOne","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-9129","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-9129","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"n/a","product":"Revive Adserver All versions before 3.2.3","version":"affected Revive Adserver All versions before 3.2.3","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2016","cve_id":"9129","vulnerable":"1","versionEndIncluding":"3.2.2","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"revive-adserver","cpe5":"revive_adserver","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"adp":[{"providerMetadata":{"dateUpdated":"2024-08-06T02:42:10.602Z","orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE"},"references":[{"tags":["x_refsource_MISC","x_transferred"],"url":"https://hackerone.com/reports/98612"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5"},{"tags":["x_refsource_MISC","x_transferred"],"url":"https://www.revive-adserver.com/security/revive-sa-2016-001/"}],"title":"CVE Program Container"}],"cna":{"affected":[{"product":"Revive Adserver All versions before 3.2.3","vendor":"n/a","versions":[{"status":"affected","version":"Revive Adserver All versions before 3.2.3"}]}],"datePublic":"2017-03-27T00:00:00.000Z","descriptions":[{"lang":"en","value":"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."}],"problemTypes":[{"descriptions":[{"cweId":"CWE-203","description":"Information Exposure Through Discrepancy (CWE-203)","lang":"en","type":"CWE"}]}],"providerMetadata":{"dateUpdated":"2017-03-28T02:57:01.000Z","orgId":"36234546-b8fa-4601-9d6f-f4e334aa8ea1","shortName":"hackerone"},"references":[{"tags":["x_refsource_MISC"],"url":"https://hackerone.com/reports/98612"},{"tags":["x_refsource_MISC"],"url":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5"},{"tags":["x_refsource_MISC"],"url":"https://www.revive-adserver.com/security/revive-sa-2016-001/"}],"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"support@hackerone.com","ID":"CVE-2016-9129","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"Revive Adserver All versions before 3.2.3","version":{"version_data":[{"version_value":"Revive Adserver All versions before 3.2.3"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"Information Exposure Through Discrepancy (CWE-203)"}]}]},"references":{"reference_data":[{"name":"https://hackerone.com/reports/98612","refsource":"MISC","url":"https://hackerone.com/reports/98612"},{"name":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5","refsource":"MISC","url":"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5"},{"name":"https://www.revive-adserver.com/security/revive-sa-2016-001/","refsource":"MISC","url":"https://www.revive-adserver.com/security/revive-sa-2016-001/"}]}}}},"cveMetadata":{"assignerOrgId":"36234546-b8fa-4601-9d6f-f4e334aa8ea1","assignerShortName":"hackerone","cveId":"CVE-2016-9129","datePublished":"2017-03-28T02:46:00.000Z","dateReserved":"2016-10-31T00:00:00.000Z","dateUpdated":"2024-08-06T02:42:10.602Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.1"},"nvd":{"publishedDate":"2017-03-28 02:59:00","lastModifiedDate":"2025-04-20 01:37:25","problem_types":["CWE-203","CWE-200","CWE-203 Information Exposure Through Discrepancy (CWE-203)"],"metrics":{"cvssMetricV30":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"3.0","vectorString":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","baseScore":5.3,"baseSeverity":"MEDIUM","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"NONE","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"NONE","availabilityImpact":"NONE"},"exploitabilityScore":3.9,"impactScore":1.4}],"cvssMetricV2":[{"source":"nvd@nist.gov","type":"Primary","cvssData":{"version":"2.0","vectorString":"AV:N/AC:L/Au:N/C:P/I:N/A:N","baseScore":5,"accessVector":"NETWORK","accessComplexity":"LOW","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE"},"baseSeverity":"MEDIUM","exploitabilityScore":10,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}]},"configurations":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:*","versionEndIncluding":"3.2.2","matchCriteriaId":"94F64F5A-ACD3-4AED-82BE-832D7B4801DA"}]}]}]},"legacy_mitre":{"record":{"CveYear":"2016","CveId":"9129","Ordinal":"1","Title":"CVE-2016-9129","CVE":"CVE-2016-9129","Year":"2016"},"notes":[{"CveYear":"2016","CveId":"9129","Ordinal":"1","NoteData":"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.","Type":"Description","Title":"CVE-2016-9129"},{"CveYear":"2016","CveId":"9129","Ordinal":"2","NoteData":"2017-03-27","Type":"Other","Title":"Published"},{"CveYear":"2016","CveId":"9129","Ordinal":"3","NoteData":"2017-03-27","Type":"Other","Title":"Modified"}]}}}