Age | Commit message (Collapse) | Author | Files | Lines |
|
SSL_ERROR_SYSCALL has been handled little stricter since curl 7.67.
(For example, 56 error occurs when server clase the connection abruptly
without a close_notify alert.)
The change is applied only in debug build for compatibility with older
peers.
However, Curl in Tizen is built with debug option.
So, Unexpected 56 error can occurs.
To avoid it, This patch creates new option and disable it.
Change-Id: I6d2b493aa1ce1ea2ce7fe1151f8948537e52c332
|
|
New test 669 checks this fix is effective.
Fixes #5256
Reported-by: thanhchungbtc on github
https://github.com/curl/curl/pull/5258/commits/96819869a975277308ef88b256f9ab9b788091f5
Change-Id: Icc77c1f01a859cb821dccc5a9cb1003e4e166117
|
|
Change-Id: Ifa484ccc2d444376bfa8c21ca8d9b63d8f48bf05
|
|
Change-Id: I37422e43c2c4c25904a4fc2a391c4a32ba3b9f5c
|
|
Change-Id: I465e6d39e1e167784bc79989c4b039721f61adc1
|
|
- bug: https://github.com/curl/curl/issues/4043
- fix: https://github.com/curl/curl/commit/c0c40ab075cdf86424dfe346a70a31b08dc651da
Change-Id: I90808233da69e8fc3d03189f8514bca1f73d90ee
|
|
The crash is observed after below patches are applied:-
Crash in upstream libcurl: https://github.com/curl/curl/commit/fb445a1e18d12f577964c9347bc5bca74b37cd08
Crash in Tizen: https://review.tizen.org/gerrit/#/c/platform/upstream/curl/+/220576
The same crash has been reported in upstream libcurl package.
Issue #1: https://github.com/curl/curl/issues/3463
Issue #2: https://github.com/curl/curl/issues/3541
Below are the solution patches are used for creating this fix
Patch #1: https://github.com/curl/curl/commit/54b201b48c90a2fb03c2baf90837c6b63adbc344
Patch #2: https://github.com/curl/curl/commit/f1af63149389cab2519b39b8056df68f5df36b91
Patch #3: https://github.com/curl/curl/commit/4015fae044ce52a639c9358e22a9e948f287c89f
Change-Id: Iaa4a05feb6a66d9781d4e7ae07297ce369744d3d
Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
|
|
This is the common pattern used in the code and by a unified approach we
avoid mistakes.
Backported patch details:
https://github.com/curl/curl/commit/dcd7e37c3a0ce108635b89cacc1e3425e57bd3bc
Change-Id: I453175ca40d8e8dfa7611f026ec7513dc230d16f
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
Follow-up to fb445a1e18d: Set conn->data explicitly to point out the
current transfer when invoking the protocol-specific disconnect function
so that it can work correctly.
Backported patch details:
https://github.com/curl/curl/commit/f3ce38739fa49008e36959aa8189c01ab1bad5b5
Change-Id: I0f86f4f9e086ebc0954f0d9935830bb93acb4090
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
Do not assume/store assocation between a given easy handle and the
connection if it can be avoided.
Long-term, the 'conn->data' pointer should probably be removed as it is a
little too error-prone. Still used very widely though.
Backported patch details:
https://github.com/curl/curl/pull/3400/commits/fb445a1e18d12f577964c9347bc5bca74b37cd08
Change-Id: I18aa2cb7097b8598c90ddf8c8c68a9fecd86e295
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
ares: remove fd from multi fd set when ares is about to close the fd
8dfb92873af9de5d883e191e0097be32c78a7d0f
Change-Id: Ic6ce203ae3609a539f70c5ae4cb1d4b3812ae80d
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
Change-Id: I8f29a511322905036005cf8df13640518c6be7bc
|
|
Change-Id: Ic067a067b2562a1b2b4f978f32f20b269abd0886
|
|
Added Curl_resolver_kill() for all three resolver modes, which only
blocks when necessary, along with test 1592 to confirm
curl_multi_remove_handle() doesn't block unless it must.
Backported patch details:
https://github.com/curl/curl/commit/84a30d0a419ad95c53cbdfc76eb2eb75d2e51835
Change-Id: I40917dbf8262249250942c9dcb71a31e6cf0df90
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
When using c-ares for asyn dns, the dns socket fd was silently closed
by c-ares without curl being aware. curl would then 'realize' the fd
has been removed at next call of Curl_resolver_getsock, and only then
notify the CURLMOPT_SOCKETFUNCTION to remove fd from its poll set with
CURL_POLL_REMOVE. At this point the fd is already closed.
By using ares socket state callback (ARES_OPT_SOCK_STATE_CB), this
patch allows curl to be notified that the fd is not longer needed
for neither for write nor read. At this point by calling
Curl_multi_closed we are able to notify multi with CURL_POLL_REMOVE
before the fd is actually closed by ares.
In asyn-ares.c Curl_resolver_duphandle we can't use ares_dup anymore
since it does not allow passing a different sock_state_cb_data
Backported patch details:
https://github.com/curl/curl/commit/6765e6d9e6a32bb4fc666d744cb57e2d55d4e13b
Change-Id: I62b2d244cb0f38a4c4a76ad804c7fd69f9222484
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
Backported Patch link:
https://github.com/curl/curl/pull/4307
Change-Id: I5b695b661cf946b74e065d1a65697e74d7ef8af6
|
|
This reverts commit 6b333876d2db240bd01e0dcec950b2d12dc8eae5.
Change-Id: Ia687599375fb2953e9df43f7195877726c5ffa29
|
|
Various functions called within Curl_http2_done() can have the
side-effect of setting the Easy connection into drain mode (by calling
drain_this()). However, the last time we unset this for a transfer (by
calling drained_transfer()) is at the beginning of Curl_http2_done().
If the Curl_easy is reused for another transfer, it is then stuck in
drain mode permanently, which in practice makes it unable to write any
data in the new transfer.
This fix moves the last call to drained_transfer() to later in
Curl_http2_done(), after the functions that could potentially call for a
drain.
Fixes #3966
Reported-by: Josie-H
Change-Id: I83ee02bf9017c9aa3d27d50580a0f89b8ec1d05d
|
|
... that could end up a double-free
CVE-2019-5481
Bug: https://curl.haxx.se/docs/CVE-2019-5481.html
Change-Id: I4eab9aceba3ad01607eb4f302200e9f949ea4312
|
|
Fixes potential buffer overflow from 'recvfrom()', should the server
return an OACK without blksize.
Bug: https://curl.haxx.se/docs/CVE-2019-5482.html
CVE-2019-5482
Change-Id: I6c63f958f4b49aa214ea4adb55c8f85a4b1606cc
|
|
bug: https://curl.haxx.se/docs/CVE-2019-5436.html
Reported-by: l00p3r on hackerone
CVE-2019-5436
Backported patch link: https://github.com/curl/curl/commit/2576003415625d7b5f0e390902f8097830b82275.patch
Change-Id: Ic6093d1d475ed9ba87e41cff315befdc3aca9c1d
Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
|
|
|
|
curl_multi_wait() was erroneously used from within
curl_easy_perform(). It could lead to it believing there was no socket
to wait for and then instead sleep for a while instead of monitoring the
socket and then miss acting on that activity as swiftly as it should
(causing an up to 1000 ms delay).
Reported-by: Antoni Villalonga
Fixes #3305
Clodes #3306
Backported patch details:
https://github.com/curl/curl/commit/d04cef9ce1d710902d90b62de01115b9bbe958bf.patch
Change-Id: I08d95e996dd9bab5d9fd7c7fe581fdb40c8a0de8
Signed-off-by: Niraj Kumar Goit <niraj.g@samsung.com>
|
|
This limits all accepted input strings passed to libcurl to be less than
CURL_MAX_INPUT_LENGTH (8000000) bytes, for these API calls:
curl_easy_setopt() and curl_url_set().
The 8000000 number is arbitrary picked and is meant to detect mistakes
or abuse, not to limit actual practical use cases. By limiting the
acceptable string lengths we also reduce the risk of integer overflows
all over.
NOTE: This does not apply to `CURLOPT_POSTFIELDS`.
Test 1559 verifies.
ClosesThis commit closes pull request #3805. #3805
CVE-2019-5435
Change-Id: I0a6d76769e1471352a477a8b1160672757a2de54
|
|
|
|
Change-Id: I77ab3d84ffae5851d9a81a8f834dfce08b34bf6f
|
|
This reverts commit 14bcc6b79f4f26ee7821f1809961bddc3a1ae63d.
Change-Id: I2fe882d909e8a4d0669ad4a5a63a856ebd0b6d53
|
|
Change-Id: If9719a2c13e7d2f37ed1d53b81f070fbfd5bc022
|
|
Change-Id: I152d19a11c8bd12e63c3e573bba73668262099e8
Signed-off-by: Cheoleun Moon <chleun.moon@samsung.com>
|
|
Bug: https://curl.haxx.se/docs/CVE-2018-16890.html
Reported-by: Wenxiang Qian
CVE-2018-16890
Backported patch details:-
Link: https://github.com/curl/curl/commit/b780b30d1377adb10bbe774835f49e9b237fb9bb.patch
Change-Id: I15fc8002280680a7cf194dd02a5d7751cc7dbc71
Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
|
|
Bug: https://curl.haxx.se/docs/CVE-2019-3822.html
Reported-by: Wenxiang Qian
CVE-2019-3822
Backported patch details:-
Link: https://github.com/curl/curl/commit/50c9484278c63b958655a717844f0721263939cc.patch
Change-Id: I40a37af26b81a4cefe4a26f19697e7a73b17eaf6
Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
|
|
If the incoming len 5, but the buffer does not have a termination
after 5 bytes, the strtol() call may keep reading through the line
buffer until is exceeds its boundary. Fix by ensuring that we are
using a bounded read with a temporary buffer on the stack.
Bug: https://curl.haxx.se/docs/CVE-2019-3823.html
Reported-by: Brian Carpenter (Geeknik Labs)
CVE-2019-3823
Backported patch details:-
Link: https://github.com/curl/curl/commit/39df4073e5413fcdbb5a38da0c1ce6f1c0ceb484.patch
Change-Id: Ie00a759a464e51ded79d2288844053740db055b4
Signed-off-by: Nishant Chaprana <n.chaprana@samsung.com>
|
|
|
|
Change-Id: I19edb6f0066af959de76d86e75eabfee29ea5c00
|
|
Change-Id: I9fd8d310e211fdeb3b0e60097b6bd81fb8e78e9b
|
|
Change-Id: Ie916d8e445e0cc69e112cee470744a96a9c84799
|
|
Change-Id: Id46d468d2dcf15ec39dabf45f5edf077a260f6f7
|
|
ipv6 option will be enabled next commit
Change-Id: Ie0e32617cf8140b6267b82548bc9b531de2f09d5
|
|
Change-Id: I409747255d59b5e67716b606ce8c377b652fe72c
|
|
This reverts commit 5ca14f8d2be7326d956b3aa61f45102c472b0392.
|
|
Change-Id: I53d34c6604be5cc01583f1b148c8fb4ad9db83e9
|
|
Response data for a handle with a large buffer might be cached and then
used with the "closure" handle when it has a smaller buffer and then the
larger cache will be copied and overflow the new smaller heap based
buffer.
Reported-by: Dario Weisser
CVE: CVE-2018-1000300
Bug: https://curl.haxx.se/docs/adv_2018-82c2.htm
Change-Id: I02d35b9494356aaec1ca1f8eab0353a58c849e11
|
|
CVE: CVE-2018-1000301
Assisted-by: Max Dymond
Detected by OSS-Fuzz.
Bug: https://curl.haxx.se/docs/adv_2018-b138.html
Bug: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7105
Change-Id: I0bd3b891aef2bf08fdb485d135e695c2eeab86a7
|
|
Change-Id: Idb324c07ce007d1949f790c75cf703ff269e342f
Signed-off-by: Cheoleun Moon <chleun.moon@samsung.com>
|
|
Change-Id: I5d53e6655bb57364d5008a1beab388b7ba53be66
|
|
Change-Id: I13eaf3ca85d8b516dbc091acae9646e705a75f5e
|
|
Change-Id: I6be132aa9b0e2b3be821aae3cdac292525a7aa09
|
|
Change-Id: I06221d49da39082f95030ab57617a1e23fbda58b
|
|
This feature will be enabled after resolving build dependency issue
Change-Id: I6b7d8292015adbe5b488210176cf19c085b0aaf1
|
|
|