-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change blossom-ci to ACL security format [skip ci] #1706
Conversation
Signed-off-by: YanxuanLiu <[email protected]>
/build |
👎 Promotion blocked, new vulnerability foundVulnerability report
When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used. This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways. Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed. Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide". |
/build |
👎 Promotion blocked, new vulnerability foundVulnerability report
When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used. This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways. Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed. Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide". |
@YanxuanLiu please add the item to internal exception list and retry thanks |
Hi @yun ***@***.***>, @yucheng ***@***.***>,
Please check this issue report.
Thanks.
发件人: github-actions[bot] ***@***.***>
日期: 星期一, 2024年6月24日 09:14
收件人: Project-MONAI/MONAILabel ***@***.***>
抄送: Nic Ma ***@***.***>, Review requested ***@***.***>
主题: Re: [Project-MONAI/MONAILabel] change blossom-ci to ACL security format [skip ci] (PR #1706)
👎 Promotion blocked, new vulnerability found
Vulnerability report
Component
Vulnerability
Description
Severity
Apache Ivy
CVE-2022-46751<https://github.com/advisories/GHSA-2jc4-r94c-rp7h>
Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.
When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.
This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.
Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.
Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".
|HIGH
Netty Project|CVE-2023-34462<https://github.com/advisories/GHSA-6mjq-h674-j845>|Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The SniHandler can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the SniHandler to allocate 16MB of heap. The SniHandler class is a handler that waits for the TLS handshake to configure a SslHandler according to the indicated server name by the ClientHello record. For this matter it allocates a ByteBuf using the value defined in the ClientHello record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the SslClientHelloHandler. This vulnerability has been fixed in version 4.1.94.Final.|MEDIUM
Netty Project|CVE-2023-44487<https://github.com/advisories/GHSA-qppj-fm5r-hxr3>|The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.|HIGH
—
Reply to this email directly, view it on GitHub<#1706 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGSCAXNK363JNBUU5PPTNBTZI5XGTAVCNFSM6AAAAABJHP6TSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGQYTCNZXGI>.
You are receiving this because your review was requested.Message ID: ***@***.***>
|
CC @mingxin ***@***.***>
发件人: Nic Ma ***@***.***>
日期: 星期一, 2024年6月24日 09:51
收件人: Project-MONAI/MONAILabel ***@***.***>, Project-MONAI/MONAILabel ***@***.***>, Yun Liu ***@***.***>, Yucheng Tang ***@***.***>
抄送: Review requested ***@***.***>
主题: Re: [Project-MONAI/MONAILabel] change blossom-ci to ACL security format [skip ci] (PR #1706)
Hi @yun ***@***.***>, @yucheng ***@***.***>,
Please check this issue report.
Thanks.
发件人: github-actions[bot] ***@***.***>
日期: 星期一, 2024年6月24日 09:14
收件人: Project-MONAI/MONAILabel ***@***.***>
抄送: Nic Ma ***@***.***>, Review requested ***@***.***>
主题: Re: [Project-MONAI/MONAILabel] change blossom-ci to ACL security format [skip ci] (PR #1706)
👎 Promotion blocked, new vulnerability found
Vulnerability report
Component
Vulnerability
Description
Severity
Apache Ivy
CVE-2022-46751<https://github.com/advisories/GHSA-2jc4-r94c-rp7h>
Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.
When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.
This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.
Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.
Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".
|HIGH
Netty Project|CVE-2023-34462<https://github.com/advisories/GHSA-6mjq-h674-j845>|Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The SniHandler can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the SniHandler to allocate 16MB of heap. The SniHandler class is a handler that waits for the TLS handshake to configure a SslHandler according to the indicated server name by the ClientHello record. For this matter it allocates a ByteBuf using the value defined in the ClientHello record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the SslClientHelloHandler. This vulnerability has been fixed in version 4.1.94.Final.|MEDIUM
Netty Project|CVE-2023-44487<https://github.com/advisories/GHSA-qppj-fm5r-hxr3>|The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.|HIGH
—
Reply to this email directly, view it on GitHub<#1706 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGSCAXNK363JNBUU5PPTNBTZI5XGTAVCNFSM6AAAAABJHP6TSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGQYTCNZXGI>.
You are receiving this because your review was requested.Message ID: ***@***.***>
|
/build |
👎 Promotion blocked, new vulnerability foundVulnerability report
|
Thanks – the risk seems to be JAVA-related. Any ideas how this may affect MONAI-related projects?
Mingxin
From: Nic Ma ***@***.***>
Date: Monday, June 24, 2024 at 09:51
To: Project-MONAI/MONAILabel ***@***.***>, Project-MONAI/MONAILabel ***@***.***>, Yun Liu ***@***.***>, Yucheng Tang ***@***.***>, Mingxin Zheng ***@***.***>
Cc: Review requested ***@***.***>
Subject: Re: [Project-MONAI/MONAILabel] change blossom-ci to ACL security format [skip ci] (PR #1706)
CC @mingxin ***@***.***>
发件人: Nic Ma ***@***.***>
日期: 星期一, 2024年6月24日 09:51
收件人: Project-MONAI/MONAILabel ***@***.***>, Project-MONAI/MONAILabel ***@***.***>, Yun Liu ***@***.***>, Yucheng Tang ***@***.***>
抄送: Review requested ***@***.***>
主题: Re: [Project-MONAI/MONAILabel] change blossom-ci to ACL security format [skip ci] (PR #1706)
Hi @yun ***@***.***>, @yucheng ***@***.***>,
Please check this issue report.
Thanks.
发件人: github-actions[bot] ***@***.***>
日期: 星期一, 2024年6月24日 09:14
收件人: Project-MONAI/MONAILabel ***@***.***>
抄送: Nic Ma ***@***.***>, Review requested ***@***.***>
主题: Re: [Project-MONAI/MONAILabel] change blossom-ci to ACL security format [skip ci] (PR #1706)
👎 Promotion blocked, new vulnerability found
Vulnerability report
Component
Vulnerability
Description
Severity
Apache Ivy
CVE-2022-46751<https://github.com/advisories/GHSA-2jc4-r94c-rp7h>
Improper Restriction of XML External Entity Reference, XML Injection (aka Blind XPath Injection) vulnerability in Apache Software Foundation Apache Ivy.This issue affects any version of Apache Ivy prior to 2.5.2.
When Apache Ivy prior to 2.5.2 parses XML files - either its own configuration, Ivy files or Apache Maven POMs - it will allow downloading external document type definitions and expand any entity references contained therein when used.
This can be used to exfiltrate data, access resources only the machine running Ivy has access to or disturb the execution of Ivy in different ways.
Starting with Ivy 2.5.2 DTD processing is disabled by default except when parsing Maven POMs where the default is to allow DTD processing but only to include a DTD snippet shipping with Ivy that is needed to deal with existing Maven POMs that are not valid XML files but are nevertheless accepted by Maven. Access can be be made more lenient via newly introduced system properties where needed.
Users of Ivy prior to version 2.5.2 can use Java system properties to restrict processing of external DTDs, see the section about "JAXP Properties for External Access restrictions" inside Oracle's "Java API for XML Processing (JAXP) Security Guide".
|HIGH
Netty Project|CVE-2023-34462<https://github.com/advisories/GHSA-6mjq-h674-j845>|Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. The SniHandler can allocate up to 16MB of heap for each channel during the TLS handshake. When the handler or the channel does not have an idle timeout, it can be used to make a TCP server using the SniHandler to allocate 16MB of heap. The SniHandler class is a handler that waits for the TLS handshake to configure a SslHandler according to the indicated server name by the ClientHello record. For this matter it allocates a ByteBuf using the value defined in the ClientHello record. Normally the value of the packet should be smaller than the handshake packet but there are not checks done here and the way the code is written, it is possible to craft a packet that makes the SslClientHelloHandler. This vulnerability has been fixed in version 4.1.94.Final.|MEDIUM
Netty Project|CVE-2023-44487<https://github.com/advisories/GHSA-qppj-fm5r-hxr3>|The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.|HIGH
—
Reply to this email directly, view it on GitHub<#1706 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGSCAXNK363JNBUU5PPTNBTZI5XGTAVCNFSM6AAAAABJHP6TSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBVGQYTCNZXGI>.
You are receiving this because your review was requested.Message ID: ***@***.***>
|
/build |
@Nic-Ma I've added the vulnerabilities to exception list. But there is still failure of build(3.11) workflow, which blocks merging PR. Could you help to check the failure? |
ping @KumoLiu Thanks. |
@YanxuanLiu I have rerun the job, it works well now. |
change to acl format (Project-MONAI#1706)
Requested by security to prevent DDOS. The new format is provided by blossom team.