{"answers":{"affected":"3 open source packages ship an affected version, including ait-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-35061 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-35061 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-35061 is a high-severity vulnerability in n/a, published on 21 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-35061 and fix it if it is affected.\n\nWhat it is: CVE-2024-35061 is a high-severity vulnerability in n/a, published on 21 May 2024. 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-2024-35061 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ait-core (PyPI): affected all versions up to 2.5.2; no fix listed\n- ait-core (PyPI): affected all versions up to 2.5.2; no fix listed\n- ait-core (PyPI): affected all versions up to 2.5.2; no fix listed\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-2024-35061/ (Markdown: https://insights.sbomify.com/CVE-2024-35061/index.md)","id":"CVE-2024-35061","markdown":"https://insights.sbomify.com/CVE-2024-35061/index.md","name":"CVE-2024-35061","record":{"aliases":["GHSA-qv6x-53jj-vw59","PYSEC-2026-1113"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"NASA AIT-Core library","requires_auth":"none","summary":"Attackers can intercept unencrypted network traffic to read data and potentially achieve remote code execution when combined with another vulnerability.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ait_core","vendor":"nasa"}],"cvss":{"score":7.3,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"NASA AIT-Core v2.5.2 was discovered to use unencrypted channels to exchange data over the network, allowing attackers to execute a man-in-the-middle attack. When chained with CVE-2024-35059, the CVE in subject leads to an unauthenticated, fully remote code execution.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"NASA AIT-Core uses unencrypted channels to exchange data over the network","id":"CVE-2024-35061","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":3,"next":{"headline":"File upload in n/a","id":"CVE-2024-35079"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.5.2"],"package":"ait-core","purl":null,"source":"GHSA-qv6x-53jj-vw59"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.5.2"],"package":"ait-core","purl":"pkg:pypi/ait-core","source":"GHSA-qv6x-53jj-vw59"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.5.2"],"package":"ait-core","purl":"pkg:pypi/ait-core","source":"PYSEC-2026-1113"}],"prev":{"headline":"Code injection in n/a","id":"CVE-2024-35060"},"products":["n/a"],"published":"2024-05-21","related":[{"cvss_score":9.8,"headline":"NASA AIT-Core vulnerable to SQL Injection","id":"CVE-2024-35056","kev_date_added":null,"published":"2024-05-21"},{"cvss_score":7.5,"headline":"NASA AIT-Core vulnerable to remote code execution","id":"CVE-2024-35057","kev_date_added":null,"published":"2024-05-21"},{"cvss_score":7.5,"headline":"NASA AIT-Core vulnerable to remote code execution","id":"CVE-2024-35058","kev_date_added":null,"published":"2024-05-21"},{"cvss_score":7.5,"headline":"NASA AIT-Core vulnerable to remote code execution","id":"CVE-2024-35059","kev_date_added":null,"published":"2024-05-21"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2024-35060","kev_date_added":null,"published":"2024-05-21"}],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["n/a"]},"summary":"Attackers can intercept unencrypted network traffic to read data and potentially achieve remote code execution when combined with another vulnerability.","url":"https://insights.sbomify.com/CVE-2024-35061/"}