We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
And $ echo "LUY9CnVyIDA=" | base64 -d > test0061.conf && ./curl -q -K test0061.conf file:///dev/null produces this leak in mime.c:
$ echo "LUY9CnVyIDA=" | base64 -d > test0061.conf && ./curl -q -K test0061.conf file:///dev/null
curl: (7) Failed to connect to 0 port 80: Connection refused ================================================================= ==2511==ERROR: LeakSanitizer: detected memory leaks Indirect leak of 448 byte(s) in 1 object(s) allocated from: #0 0x49451d in malloc (/root/curl/build2-afl/src/curl+0x49451d) #1 0x6c51eb in curl_mime_addpart /root/curl/build2-afl/lib/../../lib/mime.c:1252:28 Indirect leak of 104 byte(s) in 1 object(s) allocated from: #0 0x49451d in malloc (/root/curl/build2-afl/src/curl+0x49451d) #1 0x6c4e6c in curl_mime_init /root/curl/build2-afl/lib/../../lib/mime.c:1215:24 Indirect leak of 1 byte(s) in 1 object(s) allocated from: #0 0x49451d in malloc (/root/curl/build2-afl/src/curl+0x49451d) #1 0x6c353b in curl_mime_data /root/curl/build2-afl/lib/../../lib/mime.c:1318:18 SUMMARY: AddressSanitizer: 553 byte(s) leaked in 3 allocation(s).
Originally posted by @geeknik in #4772 (comment)
The text was updated successfully, but these errors were encountered:
I can reproduce.
Sorry, something went wrong.
curl: proper free mimepost data
25820d5
... as it could otherwise leak memory when a transfer failed. Added test 1293 to verify. Reported-by: Brian Carpenter Closes #4781
392bff4
Successfully merging a pull request may close this issue.
And
$ echo "LUY9CnVyIDA=" | base64 -d > test0061.conf && ./curl -q -K test0061.conf file:///dev/null
produces this leak in mime.c:Originally posted by @geeknik in #4772 (comment)
The text was updated successfully, but these errors were encountered: