Thursday, 2023-07-27

*** tobias-urdin-pto is now known as tobias-urdin07:34
tobias-urdinfungi: just out of curiosity, i assume this was a redhat only initiative https://www.cvedetails.com/cve/CVE-2023-3637 so there is no OSSA for the same thing even though the patches seems to be in the open already07:35
fungitobias-urdin: looks like maybe it only affected train? or at least that's all they mention patching11:34
fungiat first i thought it might be https://launchpad.net/bugs/1988026 which we never came to a decision on issuing an advisory for. it allowed authenticated users to create an unlimited number of security groups that aren't applicable to any project, so could (very slowly) fill the db. rh reserved a different cve for that though, CVE-2022-327711:38
fungisince rh's srpms aren't publicly available, it's hard to pull the patch they're using and find out, but maybe one of our colleagues there can dig up some details... d34dh0r53? dmendiza[m]? tonyb?11:40
fungithe lack of any reference to an upstream bug report either in the cve details or rh's advisory makes me think it was something that was never reported upstream, and usually the only legitimate reason for that is the vulnerability wasn't in any upstream maintained branches of the software11:41
tonybI can for sure research tomorrow. to see what patches there are and contact the authors for why it wasn't public, if that is the case11:43
fungithanks tonyb! i think i've exhausted the research options available to me as a general member of the public11:45
tonybyeah.  I don't know if the code on git.centos.org has been pulled yet.  that'd be the only public place to see  the srpms.11:48
tobias-urdinfungi: tonyb ack ty, i was just curious since there was no mention of any patches or versions if it was handled completely in the "dark"12:10
tonybyeah.  it's a good find.  more than a little distributing on the face of it12:12
fungiyes, hopefully it's as i described, the bug doesn't exist upstream in any still maintained version and the advisory simply omitted that detail12:12
fungibut it also wouldn't be the first time red hat patched bugs downstream and forgot to even forward the bug report upstream to the project (though it would be the first case i'm aware of which was treated as a security issue, if so)12:13
tonybI'll look properly tomorrow, but it looks like the fixes for 2023-3637 are those for CVE-2022-3277. https://review.opendev.org/q/Ieef7011f48cd2188d4254ff16d90a6465bbabfe312:44
tonybhttps://access.redhat.com/security/cve/CVE-2023-3637 points at https://access.redhat.com/security/cve/CVE-2022-327712:45
fungithanks, so cve-2023-3637 was created as a duplicate12:45
tonybI need to double check but at the moment it looks that way12:45
fungii guess someone got wires crossed somewhere12:45
fungiamusing since both were assigned by the same cna12:46
fungithanks for looking!12:46
tonybYeah.  We could reach out to rodolfo as he's visible in both12:46
fungitobias-urdin: ^ semi-update12:46
tonybI'll do that tomorrow12:47
fungithanks. might have helped if the rh bug report and/or cve linked to the upstream bug report12:48
fungimaybe someone in rh security can get those added12:50
tonybThe view I have does cross-link but it isn't super obvious and I may see thinsg that aren't generally visible12:50
tonybI'll see what I can do, assuming that they are indeed duplicates12:51
fungithanks again! it's not urgent12:51
tonybAll good12:52
tobias-urdincool, thanks for checking! I knew I had seen it somewhere, after checking internally we had already handled CVE-2022-327714:24

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!