protobuf: Whitelist CVE-2015-5237
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · RAHUL taya
As per below reference links this CVE issue seems to be minor and harmless and as per upstream this is not a real issue in practice.
And as per red hat this issue is marked as low severity.
1. https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-5237
2. https://security-tracker.debian.org/tracker/CVE-2015-5237
3. https://ubuntu.com/security/CVE-2015-5237
4. https://github.com/protocolbuffers/protobuf/issues/760
Thanks,
Please use the [email protected] for meta-oe patches.
-armin
Quoted 27 lines
Upstream-Status: Pending
Signed-off-by Rahul Taya <[email protected]>--- meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb | 8 ++++++++ 1 file changed, 8 insertions(+)meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb +8
-0@@ -88,3 +88,11 @@ LDFLAGS_append_arm = " -latomic" LDFLAGS_append_mips = " -latomic" LDFLAGS_append_powerpc = " -latomic" LDFLAGS_append_mipsel = " -latomic" + +# As per below links this issue is minor and harmless and +# as per upstream this is not a real issue in practice. +# https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-5237 +# https://security-tracker.debian.org/tracker/CVE-2015-5237 +# https://ubuntu.com/security/CVE-2015-5237 +# https://github.com/protocolbuffers/protobuf/issues/760 +CVE_CHECK_WHITELIST += "CVE-2015-5237"
Quoted 9 lines · Armin Kuster
Quoted 5 lines · RAHUL taya
As per below reference links this CVE issue seems to be minor and harmless and as per upstream this is not a real issue in practice.
And as per red hat this issue is marked as low severity.
Quoted 8 lines
Quoted 4 lines
1. https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-5237
2. https://security-tracker.debian.org/tracker/CVE-2015-5237
3. https://ubuntu.com/security/CVE-2015-5237
4. https://github.com/protocolbuffers/protobuf/issues/760Thanks,
Please use the [email protected]
for meta-oe patches.
Also only tag for the intended repo, in this case [meta-oe]. I can't imagine a case where you would need to tag a patch with both [OE-core] and [meta-oe]!
This maintainer gets confused easily, so if you tag a patch for [OE-core] and it is for a recipe in [meta-oe] I will waste time in a state of confusion ;-)
Steve
Quoted 32 lines
-armin
Quoted 27 lines
Upstream-Status: Pending
Signed-off-by Rahul Taya <[email protected]>--- meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb | 8 ++++++++ 1 file changed, 8 insertions(+)meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb +8
-0@@ -88,3 +88,11 @@ LDFLAGS_append_arm = " -latomic" LDFLAGS_append_mips = " -latomic" LDFLAGS_append_powerpc = " -latomic" LDFLAGS_append_mipsel = " -latomic" + +# As per below links this issue is minor and harmless and +# as per upstream this is not a real issue in practice. +# https://bugzilla.suse.com/show_bug.cgi?id=CVE-2015-5237 +# https://security-tracker.debian.org/tracker/CVE-2015-5237 +# https://ubuntu.com/security/CVE-2015-5237 +# https://github.com/protocolbuffers/protobuf/issues/760 +CVE_CHECK_WHITELIST += "CVE-2015-5237"
Hi Steve/Akuster,
I think as i have sent this patch to: [email protected] that's why this tag [OE-core] is automatically added as i have not added it .
Please do not consider this patch i will send a new one to:
And as per NVD it affects version upto 3.1 (including)
https://nvd.nist.gov/vuln/detail/CVE-2015-5237#range-6634983
Thanks and Regards,
Rahul Taya
________________________________
From: [email protected] <[email protected]> on behalf of Steve Sakoman via lists.openembedded.org <[email protected]>
Sent: Tuesday, June 15, 2021 12:14 AM
To: RAHUL taya <[email protected]>
Cc: Patches and discussions about the oe-core layer <[email protected]>; Khem Raj <[email protected]>; Nisha Parrakat <[email protected]>; Purushottam Choudhary <[email protected]>; Armin Kuster <[email protected]>
Subject: Re: [OE-core] [meta-oe][dunfell][PATCH] protobuf: Whitelist CVE-2015-5237
Quoted 9 lines · Armin Kuster
Quoted 5 lines · RAHUL taya
As per below reference links this CVE issue seems to be minor and harmless and as per upstream this is not a real issue in practice.
And as per red hat this issue is marked as low severity.
Quoted 8 lines
Quoted 4 lines
1. https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.suse.com%2Fshow_bug.cgi%3Fid%3DCVE-2015-5237&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217228847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JshJaYWDGbjS%2BKDl9edlfrVB%2BSK3bv1l1TA%2BoVj4V4k%3D&reserved=0
2. https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecurity-tracker.debian.org%2Ftracker%2FCVE-2015-5237&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217228847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=yUE0n3WsdYOfAyF3yOsDdJxpjWiOdevwJTvlddmmWG8%3D&reserved=0
3. https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fubuntu.com%2Fsecurity%2FCVE-2015-5237&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217228847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=iFCm4U0STA4Y%2F1v%2FJUP%2FMNUf%2F6hh%2FbtIdwMdMa53tl8%3D&reserved=0
4. https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprotocolbuffers%2Fprotobuf%2Fissues%2F760&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217228847%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=z8SsawnKwk224oMuShYIsQwG9fGrfzRgR1Nzj%2FnJ8Yg%3D&reserved=0Thanks,
Please use the [email protected]
for meta-oe patches.
Also only tag for the intended repo, in this case [meta-oe]. I can't imagine a case where you would need to tag a patch with both [OE-core] and [meta-oe]!
This maintainer gets confused easily, so if you tag a patch for [OE-core] and it is for a recipe in [meta-oe] I will waste time in a state of confusion ;-)
Steve
Quoted 20 lines
-armin
Quoted 19 lines
Upstream-Status: Pending
Signed-off-by Rahul Taya <[email protected]>--- meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb | 8 ++++++++ 1 file changed, 8 insertions(+)meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb +3
-0@@ -88,3 +88,11 @@ LDFLAGS_append_arm = " -latomic" LDFLAGS_append_mips = " -latomic" LDFLAGS_append_powerpc = " -latomic" LDFLAGS_append_mipsel = " -latomic" + +# As per below links this issue is minor and harmless and +# as per upstream this is not a real issue in practice.
Quoted 12 lines
meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb LDFLAGS_append_arm = " -latomic" · line 98
Quoted 8 lines
meta-oe/recipes-devtools/protobuf/protobuf_3.11.4.bb +5
-0+# https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.suse.com%2Fshow_bug.cgi%3Fid%3DCVE-2015-5237&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217238740%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4SctlXfyhEg32X7RbVLb0NJiXRHVzh4QiQANVDNWMRQ%3D&reserved=0 +# https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsecurity-tracker.debian.org%2Ftracker%2FCVE-2015-5237&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217238740%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=oOWCXMpoie6c4G01wy%2B6HV4npUDN8DKGeUkr1v%2BnjF0%3D&reserved=0 +# https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fubuntu.com%2Fsecurity%2FCVE-2015-5237&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217238740%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=L%2BYvWUGbeOxZ0XLHd1FmFJ2DxpASrpz%2Bs727%2B2%2B3XFA%3D&reserved=0 +# https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fprotocolbuffers%2Fprotobuf%2Fissues%2F760&data=04%7C01%7CRahul.Taya%40kpit.com%7C511769123a5942dcefef08d92f648e7c%7C3539451eb46e4a26a242ff61502855c7%7C0%7C0%7C637592931217238740%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=L%2Bb26sD4AhZslzqBrM4Fijme1vaLgU0z94mn0Toukf4%3D&reserved=0 +CVE_CHECK_WHITELIST += "CVE-2015-5237"
This message contains information that may be privileged or confidential and is the property of the KPIT Technologies Ltd. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. KPIT Technologies Ltd. does not accept any liability for virus infected mails.