Open cliedeman opened 8 months ago
@cliedeman
Thanks for raising this issue!
To fix this issue we can add validation code for input proposedLeaseId
in following functions, to make sure it's GUID:
Blob lease: https://github.com/Azure/Azurite/blob/d544d16f910e490fdd9db5565459df701895308f/src/blob/handlers/BlobHandler.ts#L374
https://github.com/Azure/Azurite/blob/d544d16f910e490fdd9db5565459df701895308f/src/blob/handlers/BlobHandler.ts#L506
Container lease:
https://github.com/Azure/Azurite/blob/d544d16f910e490fdd9db5565459df701895308f/src/blob/handlers/ContainerHandler.ts#L384
https://github.com/Azure/Azurite/blob/d544d16f910e490fdd9db5565459df701895308f/src/blob/handlers/ContainerHandler.ts#L548
Azurite welcome contribution! It would be great if you could raise a PR to fix this!
Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
latest as of today
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
docker
What's the Node.js version?
What problem was encountered?
Difference between azure storage account and azure
Steps to reproduce the issue?
Create a least with a non guid id Azure Error:
If possible, please provide the debug log using the -d parameter, replacing \<pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
Use a valid lease id