Closed stevenjohnstone closed 3 years ago
This issue seem to have CVE-2020-7711 assigned.
Will this issue be addressed?
Any updates on this fixing this issue? Snyk is logging a high severity security vulnerability with this repo due to this issue. Any high severity vulnerability in a library of this nature, means it is currently unsuitable for enterprise projects.
While this bug was filed against goxmldsig, it appears the test program above actually tests it using the saml2 library, and this seems to have been fixed (2 days ago) in the saml2 library. I can't get the test program to crash and it seems @russellhaering added code to make sure valid XML was being used here: https://github.com/russellhaering/gosaml2/commit/0f0fb74d103c2e42a10a5379151619502fecc57b#diff-184d234308543ccf5984a0bfe952dbde13d02450a1b1d872c19b3184b646007dR375-R376
I suppose this means goxmldsig might technically still have a CVE, but if it's being used from the saml2 library (which is my case and why I was asked to look at this), it appears to be mitigated?
Hey, sorry for the silence here. I think this was fixed as a side-effect of our resolution to another issue a few months ago, but let me push a quick fix to make it explicit.
Hey, sorry for the silence here. I think this was fixed as a side-effect of our resolution to another issue a few months ago, but let me push a quick fix to make it explicit.
Can you please confirm that 1.1.0 is not affected anymore?
Created #71 to explicitly handle the case of SignatureValue being nil which is enough to close this one out once reviewed and merged.
When will be a new release with official fix to CVE-2020-7711? It wasn't confirmed that the patch for CVE-2020-15216 also fixed this vulnerability.
Hey, sorry for the silence here. I think this was fixed as a side-effect of our resolution to another issue a few months ago, but let me push a quick fix to make it explicit.
Can you please confirm if this issue is fixed? Synk is still reporting this issue.
can you please release a security patch for CVE-2020-7711 and make it explicit? The whitesourcescan is still reporting this vulnerability in spite of having the version github.com/russellhaering/goxmldsig v1.1.0.
See https://github.com/russellhaering/gosaml2/issues/59 for background.
Program which exhibits the issue:
Panic:
Potential fix: