-
Notifications
You must be signed in to change notification settings - Fork 676
ECR: attributes are url-encoded #3038
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
Comments
Looking at this. I haven't been able to reproduce this. The image that I have handy doesn't include these packages, and the HTTP response that I see has these attributes as JSON and not URL encoded. Sample (trimmed) HTTP response from ECR
Can you print the raw HTTP response that you get? Here's a sample code on how to achieve that
At minimum, we'd like ECR to acknowledge that these fields are encoded on their docs |
@Madrigal you have simply chosen a CVE that affects a package that has a version that does not need percent encoding. Here is a raw response from a
Interestingly, the API reference DOES NOT describe those as percent encoded https://docs.aws.amazon.com/AmazonECR/latest/APIReference/API_Attribute.html So I guess the documentation also have to be fixed. UPD: oops, I didn't notice you have also provided a link, somehow the last line of your comment got into my blind spot. |
Acknowledgements
go get -u github.com/aws/aws-sdk-go-v2/...
)Describe the bug
ECR image scan findings include
ImageScanFinding.Attributes
field, that contains arbitrary key values.The problem is that those key-values are url-encoded.
Eg:
See the version contains
%7E
.I believe SDK should hide all encoding-decoding from the library user and provide ready to use data.
Regression Issue
Expected Behavior
Current Behavior
Reproduction Steps
Obtain image scan findings
types.ImageScanFindings
and read itsAttributes
Possible Solution
No response
Additional Information/Context
No response
AWS Go SDK V2 Module Versions Used
Compiler and Version used
1.24.1
Operating System and version
Ubuntu 24
The text was updated successfully, but these errors were encountered: