๐จ CVE-2021-44927
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_sg_vrml_mf_append function, which causes a segmentation fault and application crash.
๐@cveNotify
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_sg_vrml_mf_append function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_sg_vrml_mf_append() ยท Issue #1960 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44926
A null pointer dereference vulnerability exists in the gpac in the gf_node_get_tag function, which causes a segmentation fault and application crash.
๐@cveNotify
A null pointer dereference vulnerability exists in the gpac in the gf_node_get_tag function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_node_get_tag() ยท Issue #1961 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44925
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_svg_get_attribute_name function, which causes a segmentation fault and application crash.
๐@cveNotify
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_svg_get_attribute_name function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_svg_get_attribute_name() ยท Issue #1967 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44924
An infinite loop vulnerability exists in gpac 1.1.0 in the gf_log function, which causes a Denial of Service.
๐@cveNotify
An infinite loop vulnerability exists in gpac 1.1.0 in the gf_log function, which causes a Denial of Service.
๐@cveNotify
GitHub
Infinite loop in gf_log() ยท Issue #1959 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44923
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_dump_vrml_dyn_field.isra function, which causes a segmentation fault and application crash.
๐@cveNotify
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_dump_vrml_dyn_field.isra function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_dump_vrml_dyn_field.isra() ยท Issue #1962 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the latest v...
๐จ CVE-2021-44922
A null pointer dereference vulnerability exists in gpac 1.1.0 in the BD_CheckSFTimeOffset function, which causes a segmentation fault and application crash.
๐@cveNotify
A null pointer dereference vulnerability exists in gpac 1.1.0 in the BD_CheckSFTimeOffset function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in BD_CheckSFTimeOffset() ยท Issue #1969 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44921
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_isom_parse_movie_boxes_internal function, which causes a segmentation fault and application crash.
๐@cveNotify
A null pointer dereference vulnerability exists in gpac 1.1.0 in the gf_isom_parse_movie_boxes_internal function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_isom_parse_movie_boxes_internal() ยท Issue #1964 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44920
An invalid memory address dereference vulnerability exists in gpac 1.1.0 in the dump_od_to_saf.isra function, which causes a segmentation fault and application crash.
๐@cveNotify
An invalid memory address dereference vulnerability exists in gpac 1.1.0 in the dump_od_to_saf.isra function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Invalid memory address dereference in dump_od_to_saf.isra() ยท Issue #1957 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-44919
A Null Pointer Dereference vulnerability exists in the gf_sg_vrml_mf_alloc function, which causes a segmentation fault and application crash.
๐@cveNotify
A Null Pointer Dereference vulnerability exists in the gf_sg_vrml_mf_alloc function, which causes a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_sg_vrml_mf_alloc() ยท Issue #1963 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the latest v...
๐จ CVE-2021-44918
A Null Pointer Dereference vulnerability exists in gpac 1.1.0 in the gf_node_get_field function, which can cause a segmentation fault and application crash.
๐@cveNotify
A Null Pointer Dereference vulnerability exists in gpac 1.1.0 in the gf_node_get_field function, which can cause a segmentation fault and application crash.
๐@cveNotify
GitHub
Null Pointer Dereference in gf_node_get_field() ยท Issue #1968 ยท gpac/gpac
Thanks for reporting your issue. Please make sure these boxes are checked before submitting your issue - thank you! I looked for a similar issue and couldn't find any. I tried with the late...
๐จ CVE-2021-43216
Microsoft Local Security Authority Server (lsasrv) Information Disclosure Vulnerability
๐@cveNotify
Microsoft Local Security Authority Server (lsasrv) Information Disclosure Vulnerability
๐@cveNotify
๐จ CVE-2021-37605
In version 6.5 Microchip MiWi software and all previous versions including legacy products, the stack is validating only two out of four Message Integrity Check (MIC) bytes.
๐@cveNotify
In version 6.5 Microchip MiWi software and all previous versions including legacy products, the stack is validating only two out of four Message Integrity Check (MIC) bytes.
๐@cveNotify
๐จ CVE-2021-37604
In version 6.5 of Microchip MiWi software and all previous versions including legacy products, there is a possibility of frame counters being validated/updated prior to the message authentication. With this vulnerability in place, an attacker may increment the incoming frame counter values by injecting messages with a sufficiently large frame counter value and invalid payload. This results in denial of service/valid packets in the network. There is also a possibility of a replay attack in the stack.
๐@cveNotify
In version 6.5 of Microchip MiWi software and all previous versions including legacy products, there is a possibility of frame counters being validated/updated prior to the message authentication. With this vulnerability in place, an attacker may increment the incoming frame counter values by injecting messages with a sufficiently large frame counter value and invalid payload. This results in denial of service/valid packets in the network. There is also a possibility of a replay attack in the stack.
๐@cveNotify
๐จ CVE-2021-4104
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
๐@cveNotify
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
๐@cveNotify
๐จ CVE-2021-43851
Anuko Time Tracker is an open source, web-based time tracking application written in PHP. SQL injection vulnerability exist in multiple files in Time Tracker version 1.19.33.5606 and prior due to not properly checking of the "group" and "status" parameters in POST requests. Group parameter is posted along when navigating between organizational subgroups (groups.php file). Status parameter is used in multiple files to change a status of an entity such as making a project, task, or user inactive. This issue has been patched in version 1.19.33.5607. An upgrade is highly recommended. If an upgrade is not practical, introduce ttValidStatus function as in the latest version and start using it user input check blocks wherever status field is used. For groups.php fix, introduce ttValidInteger function as in the latest version and use it in the access check block in the file.
๐@cveNotify
Anuko Time Tracker is an open source, web-based time tracking application written in PHP. SQL injection vulnerability exist in multiple files in Time Tracker version 1.19.33.5606 and prior due to not properly checking of the "group" and "status" parameters in POST requests. Group parameter is posted along when navigating between organizational subgroups (groups.php file). Status parameter is used in multiple files to change a status of an entity such as making a project, task, or user inactive. This issue has been patched in version 1.19.33.5607. An upgrade is highly recommended. If an upgrade is not practical, introduce ttValidStatus function as in the latest version and start using it user input check blocks wherever status field is used. For groups.php fix, introduce ttValidInteger function as in the latest version and use it in the access check block in the file.
๐@cveNotify
GitHub
SQL injection vulnerability in multiple files
### Impact
SQL injection vulnerability existed in multiple files in Time Tracker version 1.19.33.5606 and prior due to not properly checking of the "group" and "status" paramet...
SQL injection vulnerability existed in multiple files in Time Tracker version 1.19.33.5606 and prior due to not properly checking of the "group" and "status" paramet...
๐จ CVE-2021-45046
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
๐@cveNotify
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
๐@cveNotify
๐จ CVE-2021-45105
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.
๐@cveNotify
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.
๐@cveNotify
๐จ CVE-2021-42315
Microsoft Defender for IoT Remote Code Execution Vulnerability This CVE ID is unique from CVE-2021-41365, CVE-2021-42310, CVE-2021-42311, CVE-2021-42313, CVE-2021-42314, CVE-2021-43882, CVE-2021-43889.
๐@cveNotify
Microsoft Defender for IoT Remote Code Execution Vulnerability This CVE ID is unique from CVE-2021-41365, CVE-2021-42310, CVE-2021-42311, CVE-2021-42313, CVE-2021-42314, CVE-2021-43882, CVE-2021-43889.
๐@cveNotify