Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2016-9129
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 09:49 UTC · Revision 1
Source evidence
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.
osv:CVE-2016-9129
Complete source record
{
"id": "83f5b80e964f6a406ae06c86122826be7a05e7e76f6ab1de7e9bb3710308141a",
"url": "https://osv.dev/vulnerability/CVE-2016-9129",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2016-9129",
"summary": "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.",
"evidence": "osv:CVE-2016-9129",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2016-9129",
"aliases": [
"CVE-2016-9129"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/revive-adserver/revive-adserver",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"last_affected": "e1fc268218ef914dc3c37d98b9721759f051f74f"
},
{
"fixed": "38223a841190bebd7a137c7bed84fbbcb2b0c2a5"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"last_affected": "3.2.2"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "38223a841190bebd7a137c7bed84fbbcb2b0c2a5"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v3.2.2",
"v3.2.1",
"v3.2.1-rc1",
"v3.2.0",
"v3.2.0-beta",
"v3.1.0",
"v3.1.0-beta",
"v3.0.3",
"v3.0.2",
"v3.0.1",
"v3.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2016-9129.json"
}
}
],
"modified": "2026-10-20T10:48:04.606838352Z",
"provider": "osv",
"references": [
"https://hackerone.com/reports/98612",
"https://github.com/revive-adserver/revive-adserver/commit/38223a841190bebd7a137c7bed84fbbcb2b0c2a5",
"https://www.revive-adserver.com/security/revive-sa-2016-001/"
],
"provider_metadata": {}
},
"related_cves": [
{
"value": "CVE-2016-9129",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 380006,
"published_at": "2017-03-28T02:59:00.527+00:00"
}