-
Notifications
You must be signed in to change notification settings - Fork 8.8k
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
【高危漏洞】Spring Security认证绕过漏洞(CVE-2022-22978) #4869
Comments
[INFO] -----------------------< io.seata:seata-server >------------------------ |
@Barbifer I personally understand that |
你好!如下图所示,红色方框内的版本应该是包含了5.4.9版本的,所以应该是受影响的,否则贵公司旗下的阿里云业务不会扫描出高危漏洞,同时因为此漏洞原因我们平台无法审核通过等保,请问我是应该联系阿里云的工作人员还是有其他的方式解决此问题呢,望告知,抱歉叨扰了!
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2022年8月17日(星期三) 中午12:43
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [seata/seata] 【高危漏洞】Spring Security认证绕过漏洞(CVE-2022-22978) (Issue #4869)
@Barbifer我个人理解spring-security-web:5.4.9不受影响,是吗?
—
直接回复此邮件,在 GitHub 上查看,或取消订阅。
你收到这个是因为你被提到了。消息 ID:<seata/seata/issues/4869/1217454904 @ github 。com>
|
@Barbifer Please upgrade |
OK、感谢!
…------------------ 原始邮件 ------------------
发件人: ***@***.***>;
发送时间: 2022年8月17日(星期三) 下午2:46
收件人: ***@***.***>;
抄送: ***@***.***>; ***@***.***>;
主题: Re: [seata/seata] 【高危漏洞】Spring Security认证绕过漏洞(CVE-2022-22978) (Issue #4869)
@Barbifer如有需要请升级spring-security,下一版Seata会修复。
—
直接回复此邮件,在 GitHub 上查看,或取消订阅。
你收到这个是因为你被提到了。消息 ID:<seata/seata/issues/4869/1217529500 @ github 。com>
|
plz assign to me |
@liuqiufeng I don't have permission to assign |
@liuqiufeng assign to you. |
What version should I upgrade to? |
Separate upgrades to the minimum version of
|
按照报告来看,5.4.x貌似都有这个问题 |
Ⅰ. Issue Description
在阿里云安全漏洞扫描中被扫描出的高危漏洞,在最新版本、以及v1.5.2中仍然会出现此漏洞,希望能尽快升级Spring Security到指定版本!
Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
目前此漏洞已经修复,建议受影响用户升级更新到以下修复版本:
Spring Security 5.5.x >= 5.5.7
Spring Security 5.6.x >= 5.6.4
Spring Security >= 5.7
下载链接:
https://github.com/spring-projects/spring-security/tags
Ⅴ. Anything else we need to know?
Ⅵ. Environment:
The text was updated successfully, but these errors were encountered: