commit_msg
stringlengths 1
24.2k
| commit_hash
stringlengths 2
84
⌀ | project
stringlengths 2
40
| source
stringclasses 4
values | labels
int64 0
1
| repo_url
stringlengths 26
70
⌀ | commit_url
stringlengths 74
118
⌀ | commit_date
stringlengths 25
25
⌀ |
|---|---|---|---|---|---|---|---|
patch 9.0.0035: spell dump may go beyond end of an array
Problem: Spell dump may go beyond end of an array.
Solution: Limit the word length. | 54e5fed6d27b747ff152cdb6edfb72ff60e70939 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/54e5fed6d27b747ff152cdb6edfb72ff60e70939 | 2022-07-04 13:37:07+01:00 |
patch 9.0.0045: reading past end of completion with a long line
Problem: Reading past end of completion with a long line and 'infercase'
set.
Solution: Allocate the string if needed. | caea66442d86e7bbba3bf3dc202c3c0d549b9853 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/caea66442d86e7bbba3bf3dc202c3c0d549b9853 | 2022-07-07 19:42:04+01:00 |
patch 9.0.0046: reading past end of completion with duplicate match
Problem: Reading past end of completion with duplicate match.
Solution: Check string length | baefde14550231f6468ac2ed2ed495bc381c0c92 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/baefde14550231f6468ac2ed2ed495bc381c0c92 | 2022-07-07 19:59:49+01:00 |
patch 9.0.0047: using freed memory with recursive substitute
Problem: Using freed memory with recursive substitute.
Solution: Always make a copy for reg_prev_sub. | 32acf1f1a72ebb9d8942b9c9d80023bf1bb668ea | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/32acf1f1a72ebb9d8942b9c9d80023bf1bb668ea | 2022-07-07 22:20:31+01:00 |
patch 9.0.0060: accessing uninitialized memory when completing long line
Problem: Accessing uninitialized memory when completing long line.
Solution: Terminate string with NUL. | b9e717367c395490149495cf375911b5d9de889e | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/b9e717367c395490149495cf375911b5d9de889e | 2022-07-23 06:53:08+01:00 |
patch 9.0.0061: ml_get error with nested autocommand
Problem: ml_get error with nested autocommand.
Solution: Also check line numbers for a nested autocommand. (closes #10761) | 5fa9f23a63651a8abdb074b4fc2ec9b1adc6b089 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/5fa9f23a63651a8abdb074b4fc2ec9b1adc6b089 | 2022-07-23 09:06:48+01:00 |
patch 9.0.0101: invalid memory access in diff mode with "dp" and undo
Problem: Invalid memory access in diff mode with "dp" and undo.
Solution: Make sure the line number does not go below one. | 4e677b9c40ccbc5f090971b31dc2fe07bf05541d | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/4e677b9c40ccbc5f090971b31dc2fe07bf05541d | 2022-07-28 18:44:27+01:00 |
patch 9.0.0102: reading past end of line with insert mode completion
Problem: Reading past end of line with insert mode completion.
Solution: Check text length. | a6f9e300161f4cb54713da22f65b261595e8e614 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/a6f9e300161f4cb54713da22f65b261595e8e614 | 2022-07-28 21:51:37+01:00 |
patch 9.0.0104: going beyond allocated memory when evaluating string constant
Problem: Going beyond allocated memory when evaluating string constant.
Solution: Properly skip over <Key> form. | 1e56bda9048a9625bce6e660938c834c5c15b07d | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/1e56bda9048a9625bce6e660938c834c5c15b07d | 2022-07-29 15:28:27+01:00 |
patch 9.0.0105: illegal memory access when pattern starts with illegal byte
Problem: Illegal memory access when pattern starts with illegal byte.
Solution: Do not match a character with an illegal byte. | f50940531dd57135fe60aa393ac9d3281f352d88 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/f50940531dd57135fe60aa393ac9d3281f352d88 | 2022-07-29 16:22:25+01:00 |
patch 9.0.0211: invalid memory access when compiling :lockvar
Problem: Invalid memory access when compiling :lockvar.
Solution: Don't read past the end of the line. | d1d8f6bacb489036d0fd479c9dd3c0102c988889 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/d1d8f6bacb489036d0fd479c9dd3c0102c988889 | 2022-08-14 21:28:32+01:00 |
patch 9.0.0212: invalid memory access when compiling :unlet
Problem: Invalid memory access when compiling :unlet.
Solution: Don't read past the end of the line. | dbdd16b62560413abcc3c8e893cc3010ccf31666 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/dbdd16b62560413abcc3c8e893cc3010ccf31666 | 2022-08-14 21:46:07+01:00 |
patch 9.0.0213: using freed memory with error in assert argument
Problem: Using freed memory with error in assert argument.
Solution: Make a copy of the error. | 249e1b903a9c0460d618f6dcc59aeb8c03b24b20 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/249e1b903a9c0460d618f6dcc59aeb8c03b24b20 | 2022-08-14 22:23:02+01:00 |
patch 9.0.0218: reading before the start of the line
Problem: Reading before the start of the line.
Solution: When displaying "$" check the column is not negative. | e98c88c44c308edaea5994b8ad4363e65030968c | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/e98c88c44c308edaea5994b8ad4363e65030968c | 2022-08-16 14:51:53+01:00 |
patch 9.0.0220: invalid memory access with for loop over NULL string
Problem: Invalid memory access with for loop over NULL string.
Solution: Make sure mb_ptr2len() consistently returns zero for NUL. | f6d39c31d2177549a986d170e192d8351bd571e2 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/f6d39c31d2177549a986d170e192d8351bd571e2 | 2022-08-16 17:50:38+01:00 |
patch 9.0.0221: accessing freed memory if compiling nested function fails
Problem: Accessing freed memory if compiling nested function fails.
Solution: Mess up the variable name so that it won't be found. | 1889f499a4f248cd84e0e0bf6d0d820016774494 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/1889f499a4f248cd84e0e0bf6d0d820016774494 | 2022-08-16 19:34:44+01:00 |
patch 9.0.0224: Using NULL pointer when skipping compiled code
Problem: Using NULL pointer when skipping compiled code.
Solution: Check for skipping. | 4875d6ab068f09df88d24d81de40dcd8d56e243d | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/4875d6ab068f09df88d24d81de40dcd8d56e243d | 2022-08-17 15:55:51+01:00 |
patch 9.0.0225: using freed memory with multiple line breaks in expression
Problem: Using freed memory with multiple line breaks in expression.
Solution: Free eval_tofree later. | 91c7cbfe31bbef57d5fcf7d76989fc159f73ef15 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/91c7cbfe31bbef57d5fcf7d76989fc159f73ef15 | 2022-08-18 13:28:31+01:00 |
patch 9.0.0246: using freed memory when 'tagfunc' deletes the buffer
Problem: Using freed memory when 'tagfunc' deletes the buffer.
Solution: Make a copy of the tag name. | adce965162dd89bf29ee0e5baf53652e7515762c | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/adce965162dd89bf29ee0e5baf53652e7515762c | 2022-08-22 16:35:45+01:00 |
patch 9.0.0259: crash with mouse click when not initialized
Problem: Crash with mouse click when not initialized.
Solution: Check TabPageIdxs[] is not NULL. | 80525751c5ce9ed82c41d83faf9ef38667bf61b1 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/80525751c5ce9ed82c41d83faf9ef38667bf61b1 | 2022-08-24 19:27:45+01:00 |
patch 9.0.0260: using freed memory when using 'quickfixtextfunc' recursively
Problem: Using freed memory when using 'quickfixtextfunc' recursively.
Solution: Do not allow for recursion. | d6c67629ed05aae436164eec474832daf8ba7420 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/d6c67629ed05aae436164eec474832daf8ba7420 | 2022-08-24 20:07:22+01:00 |
patch 8.1.0633: crash when out of memory while opening a terminal window
Problem: Crash when out of memory while opening a terminal window.
Solution: Handle out-of-memory more gracefully. | cd929f7ba8cc5b6d6dcf35c8b34124e969fed6b8 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/cd929f7ba8cc5b6d6dcf35c8b34124e969fed6b8 | 2018-12-24 21:38:45+01:00 |
patch 8.1.0881: can execute shell commands in rvim through interfaces
Problem: Can execute shell commands in rvim through interfaces.
Solution: Disable using interfaces in restricted mode. Allow for writing
file with writefile(), histadd() and a few others. | 8c62a08faf89663e5633dc5036cd8695c80f1075 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/8c62a08faf89663e5633dc5036cd8695c80f1075 | 2019-02-08 14:34:10+01:00 |
patch 8.1.1365: source command doesn't check for the sandbox
Problem: Source command doesn't check for the sandbox. (Armin Razmjou)
Solution: Check for the sandbox when sourcing a file. | 53575521406739cf20bbe4e384d88e7dca11f040 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/53575521406739cf20bbe4e384d88e7dca11f040 | 2019-05-22 22:38:25+02:00 |
patch 8.1.2136: using freed memory with autocmd from fuzzer
Problem: using freed memory with autocmd from fuzzer. (Dhiraj Mishra,
Dominique Pelle)
Solution: Avoid using "wp" after autocommands. (closes #5041) | ec66c41d84e574baf8009dbc0bd088d2bc5b2421 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/ec66c41d84e574baf8009dbc0bd088d2bc5b2421 | 2019-10-11 21:19:13+02:00 |
patch 8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'. | d0b5138ba4bccff8a744c99836041ef6322ed39a | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 2016-11-04 15:23:45+01:00 |
patch 8.0.0377: possible overflow when reading corrupted undo file
Problem: Possible overflow when reading corrupted undo file.
Solution: Check if allocated size is not too big. (King) | 3eb1637b1bba19519885dd6d377bd5596e91d22c | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/3eb1637b1bba19519885dd6d377bd5596e91d22c | 2017-02-26 18:11:36+01:00 |
patch 8.0.0378: possible overflow when reading corrupted undo file
Problem: Another possible overflow when reading corrupted undo file.
Solution: Check if allocated size is not too big. (King) | 0c8485f0e4931463c0f7986e1ea84a7d79f10c75 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/0c8485f0e4931463c0f7986e1ea84a7d79f10c75 | 2017-02-26 18:17:10+01:00 |
patch 8.0.1263: others can read the swap file if a user is careless
Problem: Others can read the swap file if a user is careless with his
primary group.
Solution: If the group permission allows for reading but the world
permissions doesn't, make sure the group is right. | 5a73e0ca54c77e067c3b12ea6f35e3e8681e8cf8 | vim | cvefixes | 1 | https://github.com/vim/vim | https://github.com/vim/vim/commit/5a73e0ca54c77e067c3b12ea6f35e3e8681e8cf8 | 2017-11-04 21:35:01+01:00 |
vim-patch:8.0.0056
Problem: When setting 'filetype' there is no check for a valid name.
Solution: Only allow valid characters in 'filetype', 'syntax' and 'keymap'.
https://github.com/vim/vim/commit/d0b5138ba4bccff8a744c99836041ef6322ed39a | 4fad66fbe637818b6b3d6bc5d21923ba72795040 | neovim | cvefixes | 1 | https://github.com/neovim/neovim | https://github.com/neovim/neovim/commit/4fad66fbe637818b6b3d6bc5d21923ba72795040 | 2016-11-20 14:07:46-05:00 |
zero the arep structure (Coverity #115822) | e4c00eba70a0f72c4de77b5f072c69708ec2beab | pam_tacplus | cvefixes | 1 | https://github.com/kravietz/pam_tacplus | https://github.com/kravietz/pam_tacplus/commit/e4c00eba70a0f72c4de77b5f072c69708ec2beab | 2016-05-05 19:38:34+01:00 |
pam: don't leak TACACS+ secret to journald
If journald for syslog is used, the journal is going to store everything,
even DEBUG loglevel messages. Pre-journald logging of system-wide DEBUG
loglevel could be avoided and is not affected in all cases.
With journald presence it's probably safe to no longer log sensitive
details at DEBUG level.
Fix #149
Signed-off-by: Daniel Gollub <[email protected]> | 4a9852c31c2fd0c0e72fbb689a586aabcfb11cb0 | pam_tacplus | cvefixes | 1 | https://github.com/kravietz/pam_tacplus | https://github.com/kravietz/pam_tacplus/commit/4a9852c31c2fd0c0e72fbb689a586aabcfb11cb0 | 2020-06-02 19:28:41+02:00 |
nsenter: clone /proc/self/exe to avoid exposing host binary to container
There are quite a few circumstances where /proc/self/exe pointing to a
pretty important container binary is a _bad_ thing, so to avoid this we
have to make a copy (preferably doing self-clean-up and not being
writeable).
We require memfd_create(2) -- though there is an O_TMPFILE fallback --
but we can always extend this to use a scratch MNT_DETACH overlayfs or
tmpfs. The main downside to this approach is no page-cache sharing for
the runc binary (which overlayfs would give us) but this is far less
complicated.
This is only done during nsenter so that it happens transparently to the
Go code, and any libcontainer users benefit from it. This also makes
ExtraFiles and --preserve-fds handling trivial (because we don't need to
worry about it).
Fixes: CVE-2019-5736
Co-developed-by: Christian Brauner <[email protected]>
Signed-off-by: Aleksa Sarai <[email protected]> | 0a8e4117e7f715d5fbeef398405813ce8e88558b | runc | cvefixes | 1 | https://github.com/opencontainers/runc | https://github.com/opencontainers/runc/commit/0a8e4117e7f715d5fbeef398405813ce8e88558b | 2019-02-08 18:57:59+11:00 |
Open bind mount sources from the host userns
The source of the bind mount might not be accessible in a different user
namespace because a component of the source path might not be traversed
under the users and groups mapped inside the user namespace. This caused
errors such as the following:
# time="2020-06-22T13:48:26Z" level=error msg="container_linux.go:367:
starting container process caused: process_linux.go:459:
container init caused: rootfs_linux.go:58:
mounting \"/tmp/busyboxtest/source-inaccessible/dir\"
to rootfs at \"/tmp/inaccessible\" caused:
stat /tmp/busyboxtest/source-inaccessible/dir: permission denied"
To solve this problem, this patch performs the following:
1. in nsexec.c, it opens the source path in the host userns (so we have
the right permissions to open it) but in the container mntns (so the
kernel cross mntns mount check let us mount it later:
https://github.com/torvalds/linux/blob/v5.8/fs/namespace.c#L2312).
2. in nsexec.c, it passes the file descriptors of the source to the
child process with SCM_RIGHTS.
3. In runc-init in Golang, it finishes the mounts while inside the
userns even without access to the some components of the source
paths.
Passing the fds with SCM_RIGHTS is necessary because once the child
process is in the container mntns, it is already in the container userns
so it cannot temporarily join the host mntns.
This patch uses the existing mechanism with _LIBCONTAINER_* environment
variables to pass the file descriptors from runc to runc init.
This patch uses the existing mechanism with the Netlink-style bootstrap
to pass information about the list of source mounts to nsexec.c.
Rootless containers don't use this bind mount sources fdpassing
mechanism because we can't setns() to the target mntns in a rootless
container (we don't have the privileges when we are in the host userns).
This patch takes care of using O_CLOEXEC on mount fds, and close them
early.
Fixes: #2484.
Signed-off-by: Alban Crequy <[email protected]>
Signed-off-by: Rodrigo Campos <[email protected]>
Co-authored-by: Rodrigo Campos <[email protected]> | 9c444070ec7bb83995dbc0185da68284da71c554 | runc | cvefixes | 1 | https://github.com/opencontainers/runc | https://github.com/opencontainers/runc/commit/9c444070ec7bb83995dbc0185da68284da71c554 | 2021-10-12 15:13:45+02:00 |
common: [security fix] Make sure sockets only listen locally | 4397b3376dc4e4cb1c991d0aed61ce6482614196 | libusbmuxd | cvefixes | 1 | https://github.com/libimobiledevice/libusbmuxd | https://github.com/libimobiledevice/libusbmuxd/commit/4397b3376dc4e4cb1c991d0aed61ce6482614196 | 2015-12-29 23:09:37+01:00 |
rsa_verify_hash: fix possible bleichenbacher signature attack | 5eb9743410ce4657e9d54fef26a2ee31a1b5dd09 | libtomcrypt | cvefixes | 1 | https://github.com/libtom/libtomcrypt | https://github.com/libtom/libtomcrypt/commit/5eb9743410ce4657e9d54fef26a2ee31a1b5dd09 | 2014-08-28 13:30:26+02:00 |
MDEV-26574 An improper locking bug due to unreleased lock in the ds_xbstream.cc
release lock in all as cases n xbstream_open, also fix the case where malloc would return NULL. | b1351c15946349f9daa7e5297fb2ac6f3139e4a8 | server | cvefixes | 1 | https://github.com/mariadb/server | https://github.com/mariadb/server/commit/b1351c15946349f9daa7e5297fb2ac6f3139e4a8 | 2021-09-15 14:55:45+02:00 |
MDEV-26556 An improper locking bug(s) due to unreleased lock.
Get rid of the global big_buffer. | d627d00b13ab2f2c0954ea7b77202470cb102944 | server | cvefixes | 1 | https://github.com/mariadb/server | https://github.com/mariadb/server/commit/d627d00b13ab2f2c0954ea7b77202470cb102944 | 2021-10-25 19:53:25+04:00 |
MDEV-26561 Fix a bug due to unreleased lock
Fix a bug of unreleased lock ctrl_mutex in the method create_worker_threads | e1eb39a446c30b8459c39fd7f2ee1c55a36e97d2 | server | cvefixes | 1 | https://github.com/mariadb/server | https://github.com/mariadb/server/commit/e1eb39a446c30b8459c39fd7f2ee1c55a36e97d2 | 2021-11-09 17:05:55+11:00 |
MDEV-26561 mariabackup release locks
The previous threads locked need to be released too.
This occurs if the initialization of any of the non-first
mutex/conditition variables errors occurs. | 7c30bc38a588b22b01f11130cfe99e7f36accf94 | server | cvefixes | 1 | https://github.com/mariadb/server | https://github.com/mariadb/server/commit/7c30bc38a588b22b01f11130cfe99e7f36accf94 | 2021-11-09 17:05:55+11:00 |
schannel: don't use static to store selected ciphers
CVE-2021-22897
Bug: https://curl.se/docs/CVE-2021-22897.html | bbb71507b7bab52002f9b1e0880bed6a32834511 | curl | cvefixes | 1 | https://github.com/curl/curl | https://github.com/curl/curl/commit/bbb71507b7bab52002f9b1e0880bed6a32834511 | 2021-05-24 07:56:05+02:00 |
telnet: check sscanf() for correct number of matches
CVE-2021-22898
Bug: https://curl.se/docs/CVE-2021-22898.html | 39ce47f219b09c380b81f89fe54ac586c8db6bde | curl | cvefixes | 1 | https://github.com/curl/curl | https://github.com/curl/curl/commit/39ce47f219b09c380b81f89fe54ac586c8db6bde | 2021-05-24 07:56:05+02:00 |
openssl: associate/detach the transfer from connection
CVE-2021-22901
Bug: https://curl.se/docs/CVE-2021-22901.html | 7f4a9a9b2a49547eae24d2e19bc5c346e9026479 | curl | cvefixes | 1 | https://github.com/curl/curl | https://github.com/curl/curl/commit/7f4a9a9b2a49547eae24d2e19bc5c346e9026479 | 2021-05-24 13:15:10+02:00 |
libsepol/cil: Destroy classperms list when resetting classpermission
Nicolas Iooss reports:
A few months ago, OSS-Fuzz found a crash in the CIL compiler, which
got reported as
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=28648 (the title
is misleading, or is caused by another issue that conflicts with the
one I report in this message). Here is a minimized CIL policy which
reproduces the issue:
(class CLASS (PERM))
(classorder (CLASS))
(sid SID)
(sidorder (SID))
(user USER)
(role ROLE)
(type TYPE)
(category CAT)
(categoryorder (CAT))
(sensitivity SENS)
(sensitivityorder (SENS))
(sensitivitycategory SENS (CAT))
(allow TYPE self (CLASS (PERM)))
(roletype ROLE TYPE)
(userrole USER ROLE)
(userlevel USER (SENS))
(userrange USER ((SENS)(SENS (CAT))))
(sidcontext SID (USER ROLE TYPE ((SENS)(SENS))))
(classpermission CLAPERM)
(optional OPT
(roletype nonexistingrole nonexistingtype)
(classpermissionset CLAPERM (CLASS (PERM)))
)
The CIL policy fuzzer (which mimics secilc built with clang Address
Sanitizer) reports:
==36541==ERROR: AddressSanitizer: heap-use-after-free on address
0x603000004f98 at pc 0x56445134c842 bp 0x7ffe2a256590 sp
0x7ffe2a256588
READ of size 8 at 0x603000004f98 thread T0
#0 0x56445134c841 in __cil_verify_classperms
/selinux/libsepol/src/../cil/src/cil_verify.c:1620:8
#1 0x56445134a43e in __cil_verify_classpermission
/selinux/libsepol/src/../cil/src/cil_verify.c:1650:9
#2 0x56445134a43e in __cil_pre_verify_helper
/selinux/libsepol/src/../cil/src/cil_verify.c:1715:8
#3 0x5644513225ac in cil_tree_walk_core
/selinux/libsepol/src/../cil/src/cil_tree.c:272:9
#4 0x564451322ab1 in cil_tree_walk
/selinux/libsepol/src/../cil/src/cil_tree.c:316:7
#5 0x5644513226af in cil_tree_walk_core
/selinux/libsepol/src/../cil/src/cil_tree.c:284:9
#6 0x564451322ab1 in cil_tree_walk
/selinux/libsepol/src/../cil/src/cil_tree.c:316:7
#7 0x5644512b88fd in cil_pre_verify
/selinux/libsepol/src/../cil/src/cil_post.c:2510:7
#8 0x5644512b88fd in cil_post_process
/selinux/libsepol/src/../cil/src/cil_post.c:2524:7
#9 0x5644511856ff in cil_compile
/selinux/libsepol/src/../cil/src/cil.c:564:7
The classperms list of a classpermission rule is created and filled
in when classpermissionset rules are processed, so it doesn't own any
part of the list and shouldn't retain any of it when it is reset.
Destroy the classperms list (without destroying the data in it) when
resetting a classpermission rule.
Reported-by: Nicolas Iooss <[email protected]>
Signed-off-by: James Carter <[email protected]> | f34d3d30c8325e4847a6b696fe7a3936a8a361f3 | selinux | cvefixes | 1 | https://github.com/selinuxproject/selinux | https://github.com/selinuxproject/selinux/commit/f34d3d30c8325e4847a6b696fe7a3936a8a361f3 | 2021-04-19 10:40:29-04:00 |
libsepol/cil: Destroy classperm list when resetting map perms
Map perms share the same struct as regular perms, but only the
map perms use the classperms field. This field is a pointer to a
list of classperms that is created and added to when resolving
classmapping rules, so the map permission doesn't own any of the
data in the list and this list should be destroyed when the AST is
reset.
When resetting a perm, destroy the classperms list without destroying
the data in the list.
Signed-off-by: James Carter <[email protected]> | 2d35fcc7e9e976a2346b1de20e54f8663e8a6cba | selinux | cvefixes | 1 | https://github.com/selinuxproject/selinux | https://github.com/selinuxproject/selinux/commit/2d35fcc7e9e976a2346b1de20e54f8663e8a6cba | 2021-04-19 10:40:33-04:00 |
libsepol/cil: cil_reset_classperms_set() should not reset classpermission
In struct cil_classperms_set, the set field is a pointer to a
struct cil_classpermission which is looked up in the symbol table.
Since the cil_classperms_set does not create the cil_classpermission,
it should not reset it.
Set the set field to NULL instead of resetting the classpermission
that it points to.
Signed-off-by: James Carter <[email protected]> | c49a8ea09501ad66e799ea41b8154b6770fec2c8 | selinux | cvefixes | 1 | https://github.com/selinuxproject/selinux | https://github.com/selinuxproject/selinux/commit/c49a8ea09501ad66e799ea41b8154b6770fec2c8 | 2021-04-19 10:40:35-04:00 |
libsepol/cil: Check for statements not allowed in optional blocks
While there are some checks for invalid statements in an optional
block when resolving the AST, there are no checks when building the
AST.
OSS-Fuzz found the following policy which caused a null dereference
in cil_tree_get_next_path().
(blockinherit b3)
(sid SID)
(sidorder(SID))
(optional o
(ibpkeycon :(1 0)s)
(block b3
(filecon""block())
(filecon""block())))
The problem is that the blockinherit copies block b3 before
the optional block is disabled. When the optional is disabled,
block b3 is deleted along with everything else in the optional.
Later, when filecon statements with the same path are found an
error message is produced and in trying to find out where the block
was copied from, the reference to the deleted block is used. The
error handling code assumes (rightly) that if something was copied
from a block then that block should still exist.
It is clear that in-statements, blocks, and macros cannot be in an
optional, because that allows nodes to be copied from the optional
block to somewhere outside even though the optional could be disabled
later. When optionals are disabled the AST is reset and the
resolution is restarted at the point of resolving macro calls, so
anything resolved before macro calls will never be re-resolved.
This includes tunableifs, in-statements, blockinherits,
blockabstracts, and macro definitions. Tunable declarations also
cannot be in an optional block because they are needed to resolve
tunableifs. It should be fine to allow blockinherit statements in
an optional, because that is copying nodes from outside the optional
to the optional and if the optional is later disabled, everything
will be deleted anyway.
Check and quit with an error if a tunable declaration, in-statement,
block, blockabstract, or macro definition is found within an
optional when either building or resolving the AST.
Signed-off-by: James Carter <[email protected]> | 340f0eb7f3673e8aacaf0a96cbfcd4d12a405521 | selinux | cvefixes | 1 | https://github.com/selinuxproject/selinux | https://github.com/selinuxproject/selinux/commit/340f0eb7f3673e8aacaf0a96cbfcd4d12a405521 | 2021-04-19 14:05:14-04:00 |
Fix line wrapping mode 0/3 bugs
This fixes two separate bugs:
a) Don't move a linebreak into the first symbol. This results in a empty
line at the front, which does not help to equalize line lengths at all.
Instead, merge line with the second one.
b) When moving a linebreak into a symbol that already is a break, the
number of lines must be decremented. Otherwise, uninitialized memory
is possibly used for later layout operations.
Found by fuzzer test case
id:000085,sig:11,src:003377+003350,op:splice,rep:8.
This might also affect and hopefully fix libass#229.
v2: change semantics according to review | f4f48950788b91c6a30029cc28a240b834713ea7 | libass | cvefixes | 1 | https://github.com/libass/libass | https://github.com/libass/libass/commit/f4f48950788b91c6a30029cc28a240b834713ea7 | 2016-10-05 00:38:35+02:00 |
decode_font: fix subtraction broken by change to unsigned type
This caused a one-byte buffer overwrite and an assertion failure.
Regression in commit 910211f1c0078e37546f73e95306724358b89be2.
Discovered by OSS-Fuzz.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26674.
Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26678. | 017137471d0043e0321e377ed8da48e45a3ec632 | libass | cvefixes | 1 | https://github.com/libass/libass | https://github.com/libass/libass/commit/017137471d0043e0321e377ed8da48e45a3ec632 | 2020-10-27 15:50:23+02:00 |
Fix a bug that can crash deflate on some input when using Z_FIXED.
This bug was reported by Danilo Ramos of Eideticom, Inc. It has
lain in wait 13 years before being found! The bug was introduced
in zlib 1.2.2.2, with the addition of the Z_FIXED option. That
option forces the use of fixed Huffman codes. For rare inputs with
a large number of distant matches, the pending buffer into which
the compressed data is written can overwrite the distance symbol
table which it overlays. That results in corrupted output due to
invalid distances, and can result in out-of-bound accesses,
crashing the application.
The fix here combines the distance buffer and literal/length
buffers into a single symbol buffer. Now three bytes of pending
buffer space are opened up for each literal or length/distance
pair consumed, instead of the previous two bytes. This assures
that the pending buffer cannot overwrite the symbol table, since
the maximum fixed code compressed length/distance is 31 bits, and
since there are four bytes of pending space for every three bytes
of symbol space. | 5c44459c3b28a9bd3283aaceab7c615f8020c531 | zlib | cvefixes | 1 | https://github.com/madler/zlib | https://github.com/madler/zlib/commit/5c44459c3b28a9bd3283aaceab7c615f8020c531 | 2018-04-19 19:47:11-07:00 |
[CVE-2017-0028] Fix binding of 'async' identifier in the presence of async arrow function. | 402f3d967c0a905ec5b9ca9c240783d3f2c15724 | chakracore | cvefixes | 1 | https://github.com/microsoft/chakracore | https://github.com/microsoft/chakracore/commit/402f3d967c0a905ec5b9ca9c240783d3f2c15724 | 2017-03-16 15:40:15-07:00 |
[CVE-2017-0196] Fixing an heap overread during slice.
The MissingItem check is happening on the array in a loop. It is possible that we get called into script and that mutates the array. So the Array's head is newly created with length.
However the loop is still performing over the old length.
Fixed this by checking the length In IsMissingItem function.
Added a unittest. | 065b7978c40ded35c356ced6cd922a40156c9c46 | chakracore | cvefixes | 1 | https://github.com/microsoft/chakracore | https://github.com/microsoft/chakracore/commit/065b7978c40ded35c356ced6cd922a40156c9c46 | 2017-03-16 15:40:15-07:00 |
[CVE-2017-0152] MSFT: 10592731 : Issue with Function name capturing in param scope
In a function expression with name, where the name is captured in one
of the param scope functions, if there is a function or var declaration
with the same name as the function expression name we were marking the
function expression name as shadowed. In non-eval case this causes
issue because the name symbol won't get added to the body. This change is to
fix it in such a way if the name is captured in the param scope then we
split the param and body scope such that the name symbol is added to the
param scope not body scope. | 9da019424601325a6e95e6be0fa03d7d21d0b517 | chakracore | cvefixes | 1 | https://github.com/microsoft/chakracore | https://github.com/microsoft/chakracore/commit/9da019424601325a6e95e6be0fa03d7d21d0b517 | 2017-03-16 15:40:16-07:00 |
Fix host_name_lookup (Close 2747)
Thanks to Nico R for providing a reproducing configuration.
host_lookup = *
message_size_limit = ${if def:sender_host_name {32M}{32M}}
acl_smtp_connect = acl_smtp_connect
acl_smtp_rcpt = acl_smtp_rcpt
begin acl
acl_smtp_connect:
warn ratelimit = 256 / 1m / per_conn
accept
acl_smtp_rcpt:
accept hosts = 127.0.0.*
begin routers
null:
driver = accept
transport = null
begin transports
null:
driver = appendfile
file = /dev/null
Tested with
swaks -f [email protected] -t [email protected] --pipe 'exim -bh 127.0.0.1 -C /opt/exim/etc/exim-bug.conf'
The IP must have a PTR to "localhost." to reproduce it.
(cherry picked from commit 20812729e3e47a193a21d326ecd036d67a8b2724) | d4bc023436e4cce7c23c5f8bb5199e178b4cc743 | exim | cvefixes | 1 | https://github.com/exim/exim | https://github.com/exim/exim/commit/d4bc023436e4cce7c23c5f8bb5199e178b4cc743 | 2021-05-17 12:09:31+02:00 |
Fix PAM auth. Bug 2813 | 51be321b27825c01829dffd90f11bfff256f7e42 | exim | cvefixes | 1 | https://github.com/exim/exim | https://github.com/exim/exim/commit/51be321b27825c01829dffd90f11bfff256f7e42 | 2021-10-16 16:34:03+01:00 |
Fixed div0 vulnerability in SampFact | b4e458612d4294e0cfe01dbf1c0b09a07a8133a4 | jpegsnoop | cvefixes | 1 | https://github.com/impulseadventure/jpegsnoop | https://github.com/impulseadventure/jpegsnoop/commit/b4e458612d4294e0cfe01dbf1c0b09a07a8133a4 | 2017-06-05 23:32:45-07:00 |
Fix bug #175:
CVE-2017-11661, CVE-2017-11662, CVE-2017-11663, CVE-2017-11664:
Add a new size parameter to _WM_SetupMidiEvent() so that it
knows where to stop reading, and adjust its clients properly. | ad6d7cf88d6673167ca1f517248af9409a9f1be1 | wildmidi | cvefixes | 1 | https://github.com/mindwerks/wildmidi | https://github.com/mindwerks/wildmidi/commit/ad6d7cf88d6673167ca1f517248af9409a9f1be1 | 2017-08-02 18:50:00+03:00 |
bgo#783835 - Don't divide by zero in box_blur_line() for gaussian blurs
We were making the decision to use box blurs, instead of a true
Gaussian kernel, based on the size of *both* x and y dimensions. Do
them individually instead. | ecf9267a24b2c3c0cd211dbdfa9ef2232511972a | librsvg | cvefixes | 1 | https://github.com/gnome/librsvg | https://github.com/gnome/librsvg/commit/ecf9267a24b2c3c0cd211dbdfa9ef2232511972a | 2017-06-27 17:12:51-05:00 |
Fix buffer overflow if NULL line is present in db.
If ptr->line == NULL for an entry, the first cycle will exit,
but the second one will happily write past entries buffer.
We actually do not want to exit the first cycle prematurely
on ptr->line == NULL.
Signed-off-by: Tomas Mraz <[email protected]> | 954e3d2e7113e9ac06632aee3c69b8d818cc8952 | shadow | cvefixes | 1 | https://github.com/shadow-maint/shadow | https://github.com/shadow-maint/shadow/commit/954e3d2e7113e9ac06632aee3c69b8d818cc8952 | 2017-03-31 16:25:06+02:00 |
Prevent arithmetic overflow on bounds check | 027f84c69f4ef30c0693832a6c396ef19e563ca1 | mbedtls | cvefixes | 1 | https://github.com/armmbed/mbedtls | https://github.com/armmbed/mbedtls/commit/027f84c69f4ef30c0693832a6c396ef19e563ca1 | 2018-03-13 11:29:24+01:00 |
Fix arbitrary heap exposure problem | 8f782fd8e181d9cfe9387ded43a5ca9692266b85 | json | cvefixes | 1 | https://github.com/flori/json | https://github.com/flori/json/commit/8f782fd8e181d9cfe9387ded43a5ca9692266b85 | 2017-04-18 10:38:41+02:00 |
irc: fix crash when receiving a malformed message 324 (channel mode)
Thanks to Stuart Nevans Locke for reporting the issue. | 6f4f147d8e86adf9ad34a8ffd7e7f1f23a7e74da | weechat | cvefixes | 1 | https://github.com/weechat/weechat | https://github.com/weechat/weechat/commit/6f4f147d8e86adf9ad34a8ffd7e7f1f23a7e74da | 2020-02-08 20:24:50+01:00 |
irc: fix crash when a new message 005 is received with longer nick prefixes
Thanks to Stuart Nevans Locke for reporting the issue. | 40ccacb4330a64802b1f1e28ed9a6b6d3ca9197f | weechat | cvefixes | 1 | https://github.com/weechat/weechat | https://github.com/weechat/weechat/commit/40ccacb4330a64802b1f1e28ed9a6b6d3ca9197f | 2020-02-09 20:04:45+01:00 |
auth: Do not double-expand key in passdb dict when authenticating
Broken by 79042f8c | 000030feb7a30f193197f1aab8a7b04a26b42735 | core | cvefixes | 1 | https://github.com/dovecot/core | https://github.com/dovecot/core/commit/000030feb7a30f193197f1aab8a7b04a26b42735 | 2017-03-12 20:15:13+02:00 |
lib-auth: Fix memory leak in auth_client_request_abort()
This caused memory leaks when authentication was aborted. For example
with IMAP:
a AUTHENTICATE PLAIN
*
Broken by 9137c55411aa39d41c1e705ddc34d5bd26c65021 | 1a29ed2f96da1be22fa5a4d96c7583aa81b8b060 | core | cvefixes | 1 | https://github.com/dovecot/core | https://github.com/dovecot/core/commit/1a29ed2f96da1be22fa5a4d96c7583aa81b8b060 | 2018-01-25 11:02:56+02:00 |
stream: fix SYN_SENT RST/FIN injection
RST injection during the SYN_SENT state could trick Suricata into marking
a session as CLOSED. The way this was done is: using invalid TSECR value
in RST+ACK packet. The ACK was needed to force Linux into considering the
TSECR value and compare it to the TSVAL from the SYN packet.
The second works only against Windows. The client would not use a TSVAL
but the RST packet would. Windows will reject this, but Suricata considered
the RST valid and triggered the CLOSED logic.
This patch addresses both. When the SYN packet used timestamp support
the timestamp of incoming packet is validated. Otherwise, packet responding
should not have a timestamp.
Bug #3286
Reported-by: Nicolas Adba | 9f0294fadca3dcc18c919424242a41e01f3e8318 | suricata | cvefixes | 1 | https://github.com/oisf/suricata | https://github.com/oisf/suricata/commit/9f0294fadca3dcc18c919424242a41e01f3e8318 | 2019-12-13 13:13:28+01:00 |
stream: reject broken ACK packets
Fix evasion posibility by rejecting packets with a broken ACK field.
These packets have a non-0 ACK field, but do not have a ACK flag set.
Bug #3324.
Reported-by: Nicolas Adba | fa692df37a796c3330c81988d15ef1a219afc006 | suricata | cvefixes | 1 | https://github.com/oisf/suricata | https://github.com/oisf/suricata/commit/fa692df37a796c3330c81988d15ef1a219afc006 | 2019-12-13 13:13:28+01:00 |
detect: avoid needless recursive scanning
Don't recursively inspect a detect list if the recursion
doesn't increase chance of success. | b9579fbe7dd408200ef03cbe20efddb624b73885 | suricata | cvefixes | 1 | https://github.com/oisf/suricata | https://github.com/oisf/suricata/commit/b9579fbe7dd408200ef03cbe20efddb624b73885 | 2017-05-01 11:59:03+02:00 |
stream/tcp: handle RST with MD5 or AO header
Special handling for RST packets if they have an TCP MD5 or AO header option.
The options hash can't be validated. The end host might be able to validate
it, as it can have a key/password that was communicated out of band.
The sender could use this to move the TCP state to 'CLOSED', leading to
a desync of the TCP session.
This patch builds on top of
843d0b7a10bb ("stream: support RST getting lost/ignored")
It flags the receiver as having received an RST and moves the TCP state
into the CLOSED state. It then reverts this if the sender continues to
send traffic. In this case it sets the following event:
stream-event:suspected_rst_inject;
Bug: #4710. | 50e2b973eeec7172991bf8f544ab06fb782b97df | suricata | cvefixes | 1 | https://github.com/oisf/suricata | https://github.com/oisf/suricata/commit/50e2b973eeec7172991bf8f544ab06fb782b97df | 2021-11-12 15:21:07+01:00 |
[CVE-2022-23308] Use-after-free of ID and IDREF attributes
If a document is parsed with XML_PARSE_DTDVALID and without
XML_PARSE_NOENT, the value of ID attributes has to be normalized after
potentially expanding entities in xmlRemoveID. Otherwise, later calls
to xmlGetID can return a pointer to previously freed memory.
ID attributes which are empty or contain only whitespace after
entity expansion are affected in a similar way. This is fixed by
not storing such attributes in the ID table.
The test to detect streaming mode when validating against a DTD was
broken. In connection with the defects above, this could result in a
use-after-free when using the xmlReader interface with validation.
Fix detection of streaming mode to avoid similar issues. (This changes
the expected result of a test case. But as far as I can tell, using the
XML reader with XIncludes referencing the root document never worked
properly, anyway.)
All of these issues can result in denial of service. Using xmlReader
with validation could result in disclosure of memory via the error
channel, typically stderr. The security impact of xmlGetID returning
a pointer to freed memory depends on the application. The typical use
case of calling xmlGetID on an unmodified document is not affected. | 652dd12a858989b14eed4e84e453059cd3ba340e | libxml2 | cvefixes | 1 | https://github.com/gnome/libxml2 | https://github.com/gnome/libxml2/commit/652dd12a858989b14eed4e84e453059cd3ba340e | 2022-02-19 19:26:42+01:00 |
kdc: validate sname in TGS-REQ
In tgs_build_reply(), validate the server name in the TGS-REQ is present before
dereferencing. | 04171147948d0a3636bc6374181926f0fb2ec83a | heimdal | cvefixes | 1 | https://github.com/heimdal/heimdal | https://github.com/heimdal/heimdal/commit/04171147948d0a3636bc6374181926f0fb2ec83a | 2021-08-27 11:45:41+10:00 |
fix overflow and refactor websockets decode (Hybi)
fix critical heap-based buffer overflow which allowed easy modification
of a return address via an overwritten function pointer
fix bug causing connections to fail due a "one websocket frame = one
ws_read" assumption, which failed with LibVNCServer-0.9.11
refactor websocket Hybi decode to use a simple state machine for
decoding of websocket frames | aac95a9dcf4bbba87b76c72706c3221a842ca433 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/aac95a9dcf4bbba87b76c72706c3221a842ca433 | 2017-05-14 20:38:12+02:00 |
LibVNCClient: ignore server-sent cut text longer than 1MB
This is in line with how LibVNCServer does it
(28afb6c537dc82ba04d5f245b15ca7205c6dbb9c) and fixes part of #273. | c5ba3fee85a7ecbbca1df5ffd46d32b92757bc2a | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/c5ba3fee85a7ecbbca1df5ffd46d32b92757bc2a | 2018-12-29 14:16:58+01:00 |
LibVNCClient: ignore server-sent reason strings longer than 1MB
Fixes #273 | e34bcbb759ca5bef85809967a268fdf214c1ad2c | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/e34bcbb759ca5bef85809967a268fdf214c1ad2c | 2018-12-29 14:40:53+01:00 |
LibVNCClient: fail on server-sent desktop name lengths longer than 1MB
re #273 | c2c4b81e6cb3b485fb1ec7ba9e7defeb889f6ba7 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/c2c4b81e6cb3b485fb1ec7ba9e7defeb889f6ba7 | 2019-01-06 14:20:37+01:00 |
LibVNCClient: remove now-useless cast
re #273 | a64c3b37af9a6c8f8009d7516874b8d266b42bae | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/a64c3b37af9a6c8f8009d7516874b8d266b42bae | 2019-01-06 14:22:34+01:00 |
Error out in rfbProcessFileTransferReadBuffer if length can not be allocated
re #273 | 15bb719c03cc70f14c36a843dcb16ed69b405707 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/15bb719c03cc70f14c36a843dcb16ed69b405707 | 2019-01-06 15:13:56+01:00 |
Limit lenght to INT_MAX bytes in rfbProcessFileTransferReadBuffer()
This ammends 15bb719c03cc70f14c36a843dcb16ed69b405707 fix for a heap
out-of-bound write access in rfbProcessFileTransferReadBuffer() when
reading a transfered file content in a server. The former fix did not
work on platforms with a 32-bit int type (expected by rfbReadExact()).
CVE-2018-15127
<https://github.com/LibVNC/libvncserver/issues/243>
<https://github.com/LibVNC/libvncserver/issues/273> | 09e8fc02f59f16e2583b34fe1a270c238bd9ffec | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/09e8fc02f59f16e2583b34fe1a270c238bd9ffec | 2019-01-08 10:00:24+01:00 |
libvncclient: bail out if unix socket name would overflow
Closes #291 | 3fd03977c9b35800d73a865f167338cb4d05b0c1 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/3fd03977c9b35800d73a865f167338cb4d05b0c1 | 2019-04-06 20:23:12+02:00 |
fix crash because of unaligned accesses in hybiReadAndDecode() | 0cf1400c61850065de590d403f6d49e32882fd76 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/0cf1400c61850065de590d403f6d49e32882fd76 | 2019-05-28 18:30:46+02:00 |
rfbserver: don't leak stack memory to the remote
Thanks go to Pavel Cheremushkin of Kaspersky for reporting. | d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/d01e1bb4246323ba6fcee3b82ef1faa9b1dac82a | 2019-08-19 22:32:25+02:00 |
libvncclient/cursor: limit width/height input values
Avoids a possible heap overflow reported by Pavel Cheremushkin
<[email protected]>.
re #275 | 54220248886b5001fbbb9fa73c4e1a2cb9413fed | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/54220248886b5001fbbb9fa73c4e1a2cb9413fed | 2019-11-17 17:23:03+01:00 |
libvncclient/tls_openssl: do not deref a NULL pointer
Happens in anonTLS mode where cred is NULL.
re #347 | 33441d90a506d5f3ae9388f2752901227e430553 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/33441d90a506d5f3ae9388f2752901227e430553 | 2020-03-06 17:37:57+01:00 |
libvncclient/rfbproto: limit max textchat size
Addresses GitHub Security Lab (GHSL) Vulnerability Report
`GHSL-2020-063`.
Re #275 | 8937203441ee241c4ace85da687b7d6633a12365 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/8937203441ee241c4ace85da687b7d6633a12365 | 2020-04-10 19:07:12+02:00 |
libvncclient: handle half-open TCP connections
When a connection is not reset properly at the TCP level (e.g. sudden
power loss or process crash) the TCP connection becomes half-open and
read() always returns -1 with errno = EAGAIN while select() always
returns 0. This leads to an infinite loop and can be fixed by closing
the connection after a certain number of retries (based on a timeout)
has been exceeded. | 57433015f856cc12753378254ce4f1c78f5d9c7b | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/57433015f856cc12753378254ce4f1c78f5d9c7b | 2020-04-24 15:52:05+02:00 |
libvncserver: encodings: prevent OOB accesses | 74e8a70f2c9a5248d6718ce443e07c7ed314dfff | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/74e8a70f2c9a5248d6718ce443e07c7ed314dfff | 2020-05-28 08:40:09+02:00 |
libvncserver: add missing NULL pointer checks | 38e98ee61d74f5f5ab4aa4c77146faad1962d6d0 | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/38e98ee61d74f5f5ab4aa4c77146faad1962d6d0 | 2020-05-28 08:40:09+02:00 |
libvncclient: fix pointer aliasing/alignment issue
Accessing byte-aligned data through uint32_t pointers can cause crashes
on some platforms or reduce the performance. Therefore ensure a proper
stack alignment. | 23e5cbe6b090d7f22982aee909a6a618174d3c2d | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/23e5cbe6b090d7f22982aee909a6a618174d3c2d | 2020-05-28 08:47:11+02:00 |
libvncserver: fix pointer aliasing/alignment issue
Accessing byte-aligned data through uint16_t pointers can cause crashes
on some platforms or reduce the performance. Therefore ensure a proper
stack alignment. | 53073c8d7e232151ea2ecd8a1243124121e10e2d | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/53073c8d7e232151ea2ecd8a1243124121e10e2d | 2020-05-28 08:47:11+02:00 |
libvncserver: scale: cast to 64 bit before shifting
Since pixel_value is 64 bit the data type of the shift operand should
be 64 bit too to prevent integer overflows. | a6788d1da719ae006605b78d22f5a9f170b423af | libvncserver | cvefixes | 1 | https://github.com/libvnc/libvncserver | https://github.com/libvnc/libvncserver/commit/a6788d1da719ae006605b78d22f5a9f170b423af | 2020-05-28 08:53:32+02:00 |
Fixed ngx_gmtime() on 32-bit platforms with 64-bit time_t.
In ngx_gmtime(), instead of casting to ngx_uint_t we now work with
time_t directly. This allows using dates after 2038 on 32-bit platforms
which use 64-bit time_t, notably NetBSD and OpenBSD.
As the code is not able to work with negative time_t values, argument
is now set to 0 for negative values. As a positive side effect, this
results in Epoch being used for such values instead of a date in distant
future. | 0206ebe76f748bb39d9de4dd4b3fce777fdfdccf | nginx | cvefixes | 1 | https://github.com/nginx/nginx | https://github.com/nginx/nginx/commit/0206ebe76f748bb39d9de4dd4b3fce777fdfdccf | 2017-09-13 15:52:01+03:00 |
Introduced time truncation to December 31, 9999 (ticket #1368).
Various buffers are allocated in an assumption that there would be
no more than 4 year digits. This might not be true on platforms
with 64-bit time_t, as 64-bit time_t is able to represent more than that.
Such dates with more than 4 year digits hardly make sense though, as
various date formats in use do not allow them anyway.
As such, all dates are now truncated by ngx_gmtime() to December 31, 9999.
This should have no effect on valid dates, though will prevent potential
buffer overflows on invalid ones. | b900cc28fcbb4cf5a32ab62f80b59292e1c85b4b | nginx | cvefixes | 1 | https://github.com/nginx/nginx | https://github.com/nginx/nginx/commit/b900cc28fcbb4cf5a32ab62f80b59292e1c85b4b | 2017-09-13 15:53:19+03:00 |
Mail: max_errors directive.
Similarly to smtpd_hard_error_limit in Postfix and smtp_max_unknown_commands
in Exim, specifies the number of errors after which the connection is closed. | 173f16f736c10eae46cd15dd861b04b82d91a37a | nginx | cvefixes | 1 | https://github.com/nginx/nginx | https://github.com/nginx/nginx/commit/173f16f736c10eae46cd15dd861b04b82d91a37a | 2021-05-19 03:13:31+03:00 |
5.6.1.4: Use in-memory archive instead of file IO | 0ff832d31470471803b175cfff4e40c1b08ee779 | unrar | cvefixes | 1 | https://github.com/aawc/unrar | https://github.com/aawc/unrar/commit/0ff832d31470471803b175cfff4e40c1b08ee779 | 2018-01-04 12:07:56-08:00 |
security fix | 5d43fdcd215203868d440ffc42036f5f5ffc89fc | firejail | cvefixes | 1 | https://github.com/netblue30/firejail | https://github.com/netblue30/firejail/commit/5d43fdcd215203868d440ffc42036f5f5ffc89fc | 2017-01-06 22:45:11-05:00 |
Check for presence of crsf in admin scripts | f91fbe3d94c8346884271838ae3406ae633f6f15 | ntopng | cvefixes | 1 | https://github.com/ntop/ntopng | https://github.com/ntop/ntopng/commit/f91fbe3d94c8346884271838ae3406ae633f6f15 | 2017-01-12 06:45:41-08:00 |
Security fix: prevents empty host from being used | 01f47e04fd7c8d54399c9e465f823f0017069f8f | ntopng | cvefixes | 1 | https://github.com/ntop/ntopng | https://github.com/ntop/ntopng/commit/01f47e04fd7c8d54399c9e465f823f0017069f8f | 2017-02-13 23:47:02+01:00 |
Added code to randomize values returned by rand() | 30610bda60cbfc058f90a1c0a17d0e8f4516221a | ntopng | cvefixes | 1 | https://github.com/ntop/ntopng | https://github.com/ntop/ntopng/commit/30610bda60cbfc058f90a1c0a17d0e8f4516221a | 2018-06-17 15:24:25+02:00 |
Improve security of zip/unzip sandbox by switching the sandboxed filesystem from blacklisting directories to whitelisting them. | 4ea8df7403381d9b657b121b3c98d8081b27414d | sandstorm | cvefixes | 1 | https://github.com/sandstorm-io/sandstorm | https://github.com/sandstorm-io/sandstorm/commit/4ea8df7403381d9b657b121b3c98d8081b27414d | 2017-03-01 14:23:15-08:00 |
Fix newline detection in zip paths. | 6e8572ea8bb56d0216bb1b410e5040edc051b120 | sandstorm | cvefixes | 1 | https://github.com/sandstorm-io/sandstorm | https://github.com/sandstorm-io/sandstorm/commit/6e8572ea8bb56d0216bb1b410e5040edc051b120 | 2017-03-01 14:23:15-08:00 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.