{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2025-46339","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","state":"PUBLISHED","assignerShortName":"GitHub_M","dateReserved":"2025-04-22T22:41:54.912Z","datePublished":"2025-06-04T20:04:54.504Z","dateUpdated":"2025-06-04T20:48:49.550Z"},"containers":{"cna":{"title":"FreshRSS vulnerable to favicon cache poisoning via proxy","problemTypes":[{"descriptions":[{"cweId":"CWE-349","lang":"en","description":"CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data","type":"CWE"}]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":4.3,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"LOW","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"}}],"references":[{"name":"https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-8f79-3q3w-43c4","tags":["x_refsource_CONFIRM"],"url":"https://github.com/FreshRSS/FreshRSS/security/advisories/GHSA-8f79-3q3w-43c4"},{"name":"https://github.com/FreshRSS/FreshRSS/commit/3776e1e48f33e80eb4b674bb64b419caf3b5a4e2","tags":["x_refsource_MISC"],"url":"https://github.com/FreshRSS/FreshRSS/commit/3776e1e48f33e80eb4b674bb64b419caf3b5a4e2"}],"affected":[{"vendor":"FreshRSS","product":"FreshRSS","versions":[{"version":"< 1.26.2","status":"affected"}]}],"providerMetadata":{"orgId":"a0819718-46f1-4df5-94e2-005712e83aaa","shortName":"GitHub_M","dateUpdated":"2025-06-04T20:04:54.504Z"},"descriptions":[{"lang":"en","value":"FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, it's possible to poison feed favicons by adding a given URL as a feed with the proxy set to an attacker-controlled one and disabled SSL verifying. The favicon hash is computed by hashing the feed URL and the salt, whilst not including the following variables: proxy address, proxy protocol, and whether SSL should be verified. Therefore it's possible to poison a favicon of a given feed by simply intercepting the response of the feed, and changing the website URL to one where a threat actor controls the feed favicon. Feed favicons can be replaced for all users by anyone. Version 1.26.2 fixes the issue."}],"source":{"advisory":"GHSA-8f79-3q3w-43c4","discovery":"UNKNOWN"}},"adp":[{"metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2025-06-04T20:48:40.460533Z","id":"CVE-2025-46339","options":[{"Exploitation":"poc"},{"Automatable":"no"},{"Technical Impact":"partial"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"title":"CISA ADP Vulnrichment","providerMetadata":{"orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","shortName":"CISA-ADP","dateUpdated":"2025-06-04T20:48:49.550Z"}}]}}