{"answers":{"affected":"2 open source packages ship an affected version, including com.ning:async-http-client. It affects 2 products.","exploited":"There is no known exploitation of CVE-2013-7398 in the wild and no public exploit code.","fix":"Upgrade com.ning:async-http-client to 1.9.0 or later.","what":"CVE-2013-7398 is a medium-severity vulnerability in n/a, published on 24 Jun 2015. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-7398 and fix it if it is affected.\n\nWhat it is: CVE-2013-7398 is a medium-severity vulnerability in n/a, published on 24 Jun 2015. 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-2013-7398 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.ning:async-http-client (Maven): affected all versions; fixed in 1.9.0\n- com.ning:async-http-client (Maven): affected all versions; fixed in 1.9.0\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-2013-7398/ (Markdown: https://insights.sbomify.com/CVE-2013-7398/index.md)","id":"CVE-2013-7398","markdown":"https://insights.sbomify.com/CVE-2013-7398/index.md","name":"CVE-2013-7398","record":{"aliases":["GHSA-5c66-6h6g-6q6m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java HTTP client library","requires_auth":"none","summary":"Man-in-the-middle attackers can spoof HTTPS servers because the library fails to verify hostnames in X.509 certificates.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"async-http-client","vendor":"async-http-client_project"},{"product":"jboss_fuse","vendor":"redhat"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:N/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"main/java/com/ning/http/client/AsyncHttpClientConfig.java in Async Http Client (aka AHC or async-http-client) before 1.9.0 does not require a hostname match during verification of X.509 certificates, which allows man-in-the-middle attackers to spoof HTTPS servers via an arbitrary valid certificate.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insufficient Verification of Data Authenticity in Async Http Client","id":"CVE-2013-7398","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2013"},"n_packages":2,"n_references":10,"next":{"headline":"The Direct Mail (direct_mail) TYPO3 extension improperly discloses sensitive information","id":"CVE-2013-7400"},"packages":[{"ecosystem":"Maven","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"com.ning:async-http-client","purl":null,"source":"GHSA-5c66-6h6g-6q6m"},{"ecosystem":"Maven","fixed":["1.9.0"],"introduced":["0"],"last_affected":[],"package":"com.ning:async-http-client","purl":"pkg:maven/com.ning/async-http-client","source":"GHSA-5c66-6h6g-6q6m"}],"prev":{"headline":"Insufficient Verification of Data Authenticity in Async Http Client","id":"CVE-2013-7397"},"products":["n/a"],"published":"2015-06-24","related":[{"cvss_score":4.3,"headline":"Insufficient Verification of Data Authenticity in Async Http Client","id":"CVE-2013-7397","kev_date_added":null,"published":"2015-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Man-in-the-middle attackers can spoof HTTPS servers because the library fails to verify hostnames in X.509 certificates.","url":"https://insights.sbomify.com/CVE-2013-7398/"}