CVE-2013-4208 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4208): The rsa_verify function in PuTTY before 0.63 (1) does not clear sensitive process memory after use and (2) does not free certain structures containing sensitive process memory, which might allow local users to discover private RSA and DSA keys. CVE-2013-4207 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4207): Buffer overflow in sshbn.c in PuTTY before 0.63 allows remote SSH servers to cause a denial of service (crash) via an invalid DSA signature that is not properly handled during computation of a modular inverse and triggers the overflow during a division by zero by the bignum functionality, a different vulnerability than CVE-2013-4206. CVE-2013-4206 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-4206): Heap-based buffer underflow in the modmul function in sshbn.c in PuTTY before 0.63 allows remote SSH servers to cause a denial of service (crash) and possibly trigger memory corruption or code execution via a crafted DSA signature, which is not properly handled when performing certain bit-shifting operations during modular multiplication.
I wasn't sure what to do with these; they look like they may merit a GLSA, but no bug was filed for them. Would it be appropriate to issue a GLSA update to GLSA-201308-01? Or just ignore these CVEs?
(In reply to Chris Reffett from comment #1) > I wasn't sure what to do with these; they look like they may merit a GLSA, > but no bug was filed for them. Would it be appropriate to issue a GLSA > update to GLSA-201308-01? Or just ignore these CVEs? We already rolled out GLSA on 0.63 including bug with just exactly the same severity (B2). So i vote for just closing this bug as fixed, cause our users are already updated or informed about vulnerabilities with apropriate level of severity.
Sounds good. Closing noglsa.
