{"answers":{"affected":"2 open source packages ship an affected version, including s2n-tls.","exploited":"There is no known exploitation of GHSA-857q-xmph-p2v5 in the wild and no public exploit code.","fix":"Upgrade s2n-tls to 0.3.0 or later.","what":"GHSA-857q-xmph-p2v5 is an authentication bypass vulnerability in s2n-tls, published on 9 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-857q-xmph-p2v5 and fix it if it is affected.\n\nWhat it is: GHSA-857q-xmph-p2v5 is an authentication bypass vulnerability in s2n-tls, published on 9 Aug 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 GHSA-857q-xmph-p2v5 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- s2n-tls (crates.io): affected all versions; fixed in 0.3.0\n- s2n-tls (crates.io): affected all versions; fixed in 0.3.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/GHSA-857q-xmph-p2v5/ (Markdown: https://insights.sbomify.com/GHSA-857q-xmph-p2v5/index.md)","id":"GHSA-857q-xmph-p2v5","markdown":"https://insights.sbomify.com/GHSA-857q-xmph-p2v5/index.md","name":"GHSA-857q-xmph-p2v5","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"TLS library","requires_auth":"none","summary":"An API ordering flaw in s2n-tls may skip client authentication, allowing unauthorized access if specific configuration calls are made in the wrong order.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nAn API ordering issue in s2n-tls can cause client authentication to unexpectedly not be enabled on the server when it otherwise appears to be. Server applications are impacted if client authentication is enabled by calling s2n_connection_set_config() before calling s2n_connection_set_client_auth_type().\n\nApplications are not impacted if these APIs are called in the opposite order, or if client authentication is enabled on the config with s2n_config_set_client_auth_type(). s2n-tls clients verifying server certificates are not impacted.\n\nImpacted versions: \u003c v1.5.0.\n\n### Patches\n\nThe patch is included in v1.5.0 [1].\n\n### Workarounds\n\nApplications can workaround this issue by calling s2n_connection_set_config() after calling s2n_connection_set_client_auth_type(), or by enabling client authentication on the config with s2n_config_set_client_auth_type().\n\nIf you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [2] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue.\n\n[1] https://github.com/aws/s2n-tls/releases/tag/v1.5.0\n\n[2] https://aws.amazon.com/security/vulnerability-reporting","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"s2n-tls's mTLS API ordering may skip client authentication","id":"GHSA-857q-xmph-p2v5","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"s2n-tls","purl":null,"source":"GHSA-857q-xmph-p2v5"},{"ecosystem":"crates.io","fixed":["0.3.0"],"introduced":["0"],"last_affected":[],"package":"s2n-tls","purl":"pkg:cargo/s2n-tls","source":"GHSA-857q-xmph-p2v5"}],"products":null,"published":"2024-08-09","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An API ordering flaw in s2n-tls may skip client authentication, allowing unauthorized access if specific configuration calls are made in the wrong order.","url":"https://insights.sbomify.com/GHSA-857q-xmph-p2v5/"}