{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-28971 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-28971 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-28971 is a high-severity vulnerability in Juniper Networks Paragon Active Assurance, published on 17 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-28971 and fix it if it is affected.\n\nWhat it is: CVE-2023-28971 is a high-severity vulnerability in Juniper Networks Paragon Active Assurance, published on 17 Apr 2023. 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-2023-28971 in the wild and no public exploit code.\n\nAffected product: Juniper Networks Paragon Active Assurance. 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-2023-28971/ (Markdown: https://insights.sbomify.com/CVE-2023-28971/index.md)","id":"CVE-2023-28971","markdown":"https://insights.sbomify.com/CVE-2023-28971/index.md","name":"CVE-2023-28971","record":{"aliases":["GHSA-749h-rrm4-w97r"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Network Assurance Platform","requires_auth":"none","summary":"Enabling the optional timescaledb feature on on-prem Control Centers bypasses firewall rules, allowing Test Agents to communicate with restricted internal endpoints.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"paragon_active_assurance","vendor":"juniper"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"An Improper Restriction of Communication Channel to Intended Endpoints vulnerability in the timescaledb feature of Juniper Networks Paragon Active Assurance (PAA) (Formerly Netrounds) allows an attacker to bypass existing firewall rules and limitations used to restrict internal communcations. The Test Agents (TA) Appliance connects to the Control Center (CC) using OpenVPN. TA's are assigned an internal IP address in the 100.70.0.0/16 range. Firewall rules exists to limit communication from TA's to the CC to specific services only. OpenVPN is configured to not allow direct communication between Test Agents in the OpenVPN application itself, and routing is normally not enabled on the server running the CC application. The timescaledb feature is installed as an optional package on the Control Center. When the timescaledb container is started, this causes side-effects by bypassing the existing firewall rules and limitations for Test Agent communications. Note: This issue only affects customers hosting their own on-prem Control Center. The Paragon Active Assurance Software as a Service (SaaS) is not affected by this vulnerability since the timescaledb service is not enabled. This issue affects all on-prem versions of Juniper Networks Paragon Active Assurance prior to 4.1.2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Paragon Active Assurance: Enabling the timescaledb enables IP forwarding","id":"CVE-2023-28971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Junos OS: NFX Series: 'set system ports console insecure' allows root password recovery","id":"CVE-2023-28972"},"packages":[],"prev":{"headline":"Junos OS: JRR200: Kernel crash upon receipt of a specific packet","id":"CVE-2023-28970"},"products":["Paragon Active Assurance"],"published":"2023-04-17","related":[],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-06","vendors":["Juniper Networks"]},"summary":"Enabling the optional timescaledb feature on on-prem Control Centers bypasses firewall rules, allowing Test Agents to communicate with restricted internal endpoints.","url":"https://insights.sbomify.com/CVE-2023-28971/"}