-
Notifications
You must be signed in to change notification settings - Fork 170
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
go-autorest v9.1.0
: Update module to v14.2.0
to address authorization bypass in jwt-go
#2927
Comments
go-autorest v9.1.0
: Update module to v14.2.0
address authorization bypass in github.com/dgrijalva/jwt-gogo-autorest v9.1.0
: Update module to v14.2.0
to address authorization bypass in jwt-go
@bgilbert you've touched the Azure code most recently (and generally are knowledgeable about |
I'm not an SME on the Azure authentication code, but SGTM. |
The https://github.com/Azure/go-autorest repo mentions:
It's possible that updating the SDK ( |
So should I try updating the Azure-SDK-for-go and then work on fixing any issues that come up in mantle/platform/Azure/api.go? |
Oh I see. We consume it directly (not indirectly) in
So we'll have to find a replacement for that. |
OK. This page says:
Which is already a part of |
After updating
Upon further investigation, I have found that the file According to this page, storage is deprecated and replaced by azblob |
The go-autorest dependency in Mantle is currently using v9.1.0 which uses jwt-go the vulnerable dependency.
COSA build
fails at any version after v9.10.0 since there is a change in package structure. SpecificallyBuilding Ore
fails. The switch from jwt (insecure) to jwt(secure) for go-autorest occurs in the v14.2.0 documented over here .The function used in the the current v9.1.0 called GetClientSetup() used in coreos-assembler/mantle/platform/api/azure/api.go is now replaced by several functions GetEnvironmentSettings(), NewAuthorizerFromFile(), GetSettingsFromFile().
To reproduce the fail in building COSA:
Results in
I am working on changing the function calls to update them from v9.1.0 to v14.2.0.
Let me know if anyone has questions, issues, concerns, advice.
The text was updated successfully, but these errors were encountered: