{"answers":{"affected":"2 open source packages ship an affected version, including yiisoft/yii2-redis. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48493 in the wild and no public exploit code.","fix":"Upgrade yiisoft/yii2-redis to 2.0.20 or later.","what":"CVE-2025-48493 is a medium-severity vulnerability in yiisoft yii2-redis, published on 5 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48493 and fix it if it is affected.\n\nWhat it is: CVE-2025-48493 is a medium-severity vulnerability in yiisoft yii2-redis, published on 5 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48493 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- yiisoft/yii2-redis (Packagist): affected all versions; fixed in 2.0.20\n- yiisoft/yii2-redis (Packagist): affected all versions; fixed in 2.0.20\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-2025-48493/ (Markdown: https://insights.sbomify.com/CVE-2025-48493/index.md)","id":"CVE-2025-48493","markdown":"https://insights.sbomify.com/CVE-2025-48493/index.md","name":"CVE-2025-48493","record":{"aliases":["GHSA-g3p6-82vc-43jh"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Yii 2 Redis extension","requires_auth":"high_privilege","summary":"An attacker with log access can read Redis credentials exposed in plain text during connection failures in the Yii 2 Redis extension.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"yii2-redis","vendor":"yiiframework"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:H","version":"4.0"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"The Yii 2 Redis extension provides the redis key-value store support for the Yii framework 2.0. On failing connection, the extension writes commands sequence to logs. Prior to version 2.0.20, AUTH parameters are written in plain text exposing username and password. That might be an issue if attacker has access to logs. Version 2.0.20 fixes the issue.","ecosystems":["Packagist"],"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":"Yii 2 Redis may expose AUTH paramters in logs in case of connection failure","id":"CVE-2025-48493","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":2,"n_references":2,"next":{"headline":"Gokapi vulnerable to stored XSS via uploading file with malicious file name","id":"CVE-2025-48494"},"packages":[{"ecosystem":"Packagist","fixed":["2.0.20"],"introduced":["0"],"last_affected":[],"package":"yiisoft/yii2-redis","purl":null,"source":"GHSA-g3p6-82vc-43jh"},{"ecosystem":"Packagist","fixed":["2.0.20"],"introduced":["0"],"last_affected":[],"package":"yiisoft/yii2-redis","purl":"pkg:composer/yiisoft/yii2-redis","source":"GHSA-g3p6-82vc-43jh"}],"prev":{"headline":"GetSimple CMS RCE in Edit component","id":"CVE-2025-48492"},"products":["yii2-redis"],"published":"2025-06-05","related":[],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-09","vendors":["yiisoft"]},"summary":"An attacker with log access can read Redis credentials exposed in plain text during connection failures in the Yii 2 Redis extension.","url":"https://insights.sbomify.com/CVE-2025-48493/"}