{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2021:0194-1 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"SUSE-SU-2021:0194-1 is a vulnerability in stunnel, published on 22 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for SUSE-SU-2021:0194-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2021:0194-1 is a vulnerability in stunnel, published on 22 Jan 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of SUSE-SU-2021:0194-1 in the wild and no public exploit code.\n\nAffected product: stunnel. 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/SUSE-SU-2021-0194-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2021-0194-1/index.md)","id":"SUSE-SU-2021:0194-1","markdown":"https://insights.sbomify.com/SUSE-SU-2021-0194-1/index.md","name":"SUSE-SU-2021:0194-1","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SSL/TLS tunneling software","requires_auth":"none","summary":"An attacker can bypass certificate chain verification in stunnel when the redirect option is used with verifyChain enabled, potentially allowing man-in-the-middle attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for stunnel fixes the following issues:\n\nSecurity issue fixed:\n\n- The 'redirect' option was fixed to properly handle 'verifyChain = yes' (bsc#1177580).\n\nNon-security issues fixed:\n\n- Fix startup problem of the stunnel daemon (bsc#1178533)\n\n- update to 5.57:\n  * Security bugfixes\n  * New features\n    - New securityLevel configuration file option.\n    - Support for modern PostgreSQL clients\n    - TLS 1.3 configuration updated for better compatibility.\n  * Bugfixes\n    - Fixed a transfer() loop bug.\n    - Fixed memory leaks on configuration reloading errors.\n    - DH/ECDH initialization restored for client sections.\n    - Delay startup with systemd until network is online.\n    - A number of testing framework fixes and improvements.\n\n- update to 5.56:\n  - Various text files converted to Markdown format.\n  - Support for realpath(3) implementations incompatible\n    with POSIX.1-2008, such as 4.4BSD or Solaris.\n  - Support for engines without PRNG seeding methods (thx to\n    Petr Mikhalitsyn).\n  - Retry unsuccessful port binding on configuration\n    file reload.\n  - Thread safety fixes in SSL_SESSION object handling.\n  - Terminate clients on exit in the FORK threading model.\n\n- Fixup stunnel.conf handling:\n  * Remove old static openSUSE provided stunnel.conf.\n  * Use upstream stunnel.conf and tailor it for openSUSE using sed.\n  * Don't show README.openSUSE when installing.\n\n- enable /etc/stunnel/conf.d\n- re-enable openssl.cnf","ecosystems":["SUSE:Linux Enterprise Module for Server Applications 15 SP2"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for stunnel","id":"SUSE-SU-2021:0194-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"SUSE:Linux Enterprise Module for Server Applications 15 SP2","fixed":["5.57-3.5.1"],"introduced":["0"],"last_affected":[],"package":"stunnel","purl":"pkg:rpm/suse/stunnel\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20Server%20Applications%2015%20SP2","source":"SUSE-SU-2021:0194-1"}],"products":null,"published":"2021-01-22","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker can bypass certificate chain verification in stunnel when the redirect option is used with verifyChain enabled, potentially allowing man-in-the-middle attacks.","url":"https://insights.sbomify.com/SUSE-SU-2021-0194-1/"}