{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22873 exists.","fix":"No fix has been published for CVE-2021-22873 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22873 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 21 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-22873 and fix it if it is affected.\n\nWhat it is: CVE-2021-22873 is a medium-severity vulnerability in Revive-Adserver Revive Adserver, published on 21 Jan 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22873 exists.\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-2021-22873/ (Markdown: https://insights.sbomify.com/CVE-2021-22873/index.md)","id":"CVE-2021-22873","markdown":"https://insights.sbomify.com/CVE-2021-22873/index.md","name":"CVE-2021-22873","record":{"aliases":["GHSA-8rwp-72pf-cq9g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ad server software","requires_auth":"none","summary":"Attackers can exploit open redirects in Revive Adserver delivery scripts to redirect users to malicious sites, bypassing security controls.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"revive_adserver","vendor":"revive-adserver"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"description":"Revive Adserver before 5.1.0 is vulnerable to open redirects via the `dest`, `oadest`, and/or `ct0` parameters of the lg.php and ck.php delivery scripts. Such open redirects had previously been available by design to allow third party ad servers to track such metrics when delivering ads. However, third party click tracking via redirects is not a viable option anymore, leading to such open redirect functionality being removed and reclassified as a vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2021/CVE-2021-22873.yaml","stars":null,"title":"Revive Adserver \u003c5.1.0 - Open Redirect"}],"tier":"weaponised"},"has_fix":false,"headline":"Open redirect in https://github.com/revive-adserver/revive-adserver","id":"CVE-2021-22873","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"revive-adserver:revive_adserver","products":["revive-adserver:revive_adserver"],"type":"open_redirect","year":"2021"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in https://github.com/revive-adserver/revive-adserver","id":"CVE-2021-22874"},"packages":[],"prev":{"headline":"Cross-site scripting in https://github.com/revive-adserver/revive-adserver","id":"CVE-2021-22872"},"products":["https://github.com/revive-adserver/revive-adserver"],"published":"2021-01-21","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Attackers can exploit open redirects in Revive Adserver delivery scripts to redirect users to malicious sites, bypassing security controls.","url":"https://insights.sbomify.com/CVE-2021-22873/"}