{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2003-0316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2003-0316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2003-0316 is a medium-severity vulnerability in n/a, published on 17 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2003-0316 and fix it if it is affected.\n\nWhat it is: CVE-2003-0316 is a medium-severity vulnerability in n/a, published on 17 May 2003. 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-2003-0316 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2003-0316/ (Markdown: https://insights.sbomify.com/CVE-2003-0316/index.md)","id":"CVE-2003-0316","markdown":"https://insights.sbomify.com/CVE-2003-0316/index.md","name":"CVE-2003-0316","record":{"aliases":["GHSA-59p9-r554-rp7m"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Venturi Wireless client","requires_auth":"none","summary":"The Venturi Client acts as an open proxy and SMTP relay, allowing attackers to abuse it for spamming and unauthorized network access.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"venturi_client","vendor":"fourelle_venturi_wireless"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[],"description":"Venturi Client before 2.2, as used in certain Fourelle and Venturi Wireless products, can be used as an open proxy for various protocols, including an open relay for SMTP, which allows it to be abused by spammers.","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":"Misconfiguration in n/a","id":"CVE-2003-0316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2003"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2003-0317"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2003-0315"},"products":["n/a"],"published":"2003-05-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"The Venturi Client acts as an open proxy and SMTP relay, allowing attackers to abuse it for spamming and unauthorized network access.","url":"https://insights.sbomify.com/CVE-2003-0316/"}