X11vnc x11-less fixes and uprev #120
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jeff-dagenais
force-pushed
the
x11vnc-fixes
branch
from
6ea1ba5
to
b1c70e5
Compare
added 2 commits
February 12, 2019 11:22
There is just no point in Xdummy if x11 is not in DISTRO_FEATURES.
jeff-dagenais
force-pushed
the
x11vnc-fixes
branch
from
b1c70e5
to
a2172fb
Compare
kraj
pushed a commit
to YoeDistro/meta-openembedded
that referenced
this pull request
Jan 17, 2022
Changelog: ========= * Fixed: [CVE-2021-46141] Fix a bug affecting both uriNormalizeSyntax* and uriMakeOwner* functions where the text range in .hostText would not be duped using malloc but remain unchanged (and hence "not owned") for URIs with an IPv4 or IPv6 address hostname; depending on how an application uses uriparser, this could lead the application into a use-after-free situation. As the second half, fix uriFreeUriMembers* functions that would not free .hostText memory for URIs with an IPv4 or IPv6 address host; also, calling uriFreeUriMembers* multiple times on a URI of this very nature would result in trying to free pointers to stack (rather than heap) memory (GitHub openembedded#121, GitHub openembedded#124) Commit 987b046e41f407d17c622e580fc82a5e834b4329 Commit b1a34743bc1472e055d886e29e9b53f670eb3282 * Fixed: [CVE-2021-46142] Fix functions uriNormalizeSyntax* for out-of-memory situations (i.e. malloc returning NULL) for URIs containing empty segments (any of user info, host text, query, or fragment) where previously pointers to stack (rather than heap) memory were freed (GitHub openembedded#122, GitHub openembedded#124) Commit c0483990e6b5b454f7c8752b36760cfcb0d093f5 * Fixed: CMake: Call "enable_language(CXX)" prior to tinkering with CMAKE_CXX_* variables (GitHub openembedded#110) * Fixed: CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_INCLUDEDIR (GitHub openembedded#114) * Fixed: Windows: Address MSVC compiler warnings (GitHub openembedded#111, GitHub openembedded#113) * Fixed: Documentation: Space requirements for uriUriStringToUnixFilename did not take into account short form "file:/bin/bash" of RFC 8089 of 2017 (with prefix "file:/" rather than "file:///") that uriparser supports since release 0.8.6 in 2018 (GitHub openembedded#118, GitHub openembedded#119) * Fixed: Compile error with MinGW GCC 9 related to a mismatched prototype for function inet_ntop (GitHub openembedded#117, GitHub openembedded#120) * Fixed: Compile warnings in test suite code (GitHub openembedded#120) * Improved: Respect variable ${CPP} in doc/preprocess.sh (GitHub openembedded#115) * Added: Test suite invocation for MinGW using Wine (GitHub openembedded#120) * Soname: 1:29:0 - see https://verbump.de/ for what these numbers do Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
halstead
pushed a commit
that referenced
this pull request
Jan 18, 2022
Changelog: ========= * Fixed: [CVE-2021-46141] Fix a bug affecting both uriNormalizeSyntax* and uriMakeOwner* functions where the text range in .hostText would not be duped using malloc but remain unchanged (and hence "not owned") for URIs with an IPv4 or IPv6 address hostname; depending on how an application uses uriparser, this could lead the application into a use-after-free situation. As the second half, fix uriFreeUriMembers* functions that would not free .hostText memory for URIs with an IPv4 or IPv6 address host; also, calling uriFreeUriMembers* multiple times on a URI of this very nature would result in trying to free pointers to stack (rather than heap) memory (GitHub #121, GitHub #124) Commit 987b046e41f407d17c622e580fc82a5e834b4329 Commit b1a34743bc1472e055d886e29e9b53f670eb3282 * Fixed: [CVE-2021-46142] Fix functions uriNormalizeSyntax* for out-of-memory situations (i.e. malloc returning NULL) for URIs containing empty segments (any of user info, host text, query, or fragment) where previously pointers to stack (rather than heap) memory were freed (GitHub #122, GitHub #124) Commit c0483990e6b5b454f7c8752b36760cfcb0d093f5 * Fixed: CMake: Call "enable_language(CXX)" prior to tinkering with CMAKE_CXX_* variables (GitHub #110) * Fixed: CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR and CMAKE_INSTALL_INCLUDEDIR (GitHub #114) * Fixed: Windows: Address MSVC compiler warnings (GitHub #111, GitHub #113) * Fixed: Documentation: Space requirements for uriUriStringToUnixFilename did not take into account short form "file:/bin/bash" of RFC 8089 of 2017 (with prefix "file:/" rather than "file:///") that uriparser supports since release 0.8.6 in 2018 (GitHub #118, GitHub #119) * Fixed: Compile error with MinGW GCC 9 related to a mismatched prototype for function inet_ntop (GitHub #117, GitHub #120) * Fixed: Compile warnings in test suite code (GitHub #120) * Improved: Respect variable ${CPP} in doc/preprocess.sh (GitHub #115) * Added: Test suite invocation for MinGW using Wine (GitHub #120) * Soname: 1:29:0 - see https://verbump.de/ for what these numbers do Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This series allows to use x11vnc with fbdev or other x11-less configuration by honouring the lack of
x11in the DISTRO_FEATURES.