Severity HIGH security problem to be announced with curl 8.4.0 on Oct 11

Re:Severity HIGH security problem to be announced with curl ... by jddj on Thursday October 05, 2023 @06:53AM (#37777011)

> Updating the shared libcurl library should be enough to fix this issue on all operating systems.

> Then again there will also be countless docker (and similar) images that feature their own copies, so there will still be quite a large number of rebuilds necessary I bet.

Quite a large number, yeah.

[ Parent | on HN ]

Re:Severity HIGH security problem to be announced with curl ... by nerdponx on Thursday October 05, 2023 @07:21AM (#37777177)

Including mine once the security team sees the CVE warning, even though our image literally never uses curl or libcurl and only ever communicates with other internal systems, within our private network.

Not that we shouldn't patch it! But unless the nasal demons are going to start a process and make unwanted HTTP connections, I'm not worried.

[ Parent | on HN ]

Re:Severity HIGH security problem to be announced with curl ... by hhh on Thursday October 05, 2023 @08:36AM (#37777797)

Why do you include it if it’s unused?

[ Parent | on HN ]

Re:Severity HIGH security problem to be announced with curl ... by mschuster91 on Thursday October 05, 2023 @02:11PM (#37781962)

A lot of stuff depends on cURL/libcurl. IIRC, php these days has it enabled by default.

[ Parent | on HN ]

Re:Severity HIGH security problem to be announced with curl ... by scrpl on Thursday October 05, 2023 @08:21AM (#37777656)

And embedded systems (cars and stuff)...

[ Parent | on HN ]