‼ CVE-2022-1473 ‼
📖 Read
via "National Vulnerability Database".
The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the memory occuppied by the removed hash table entries. This function is used when decoding certificates or keys. If a long lived process periodically decodes certificates or keys its memory usage will expand without bounds and the process might be terminated by the operating system causing a denial of service. Also traversing the empty hash table entries will take increasingly more time. Typically such long lived processes might be TLS clients or TLS servers configured to accept client certificate authentication. The function was added in the OpenSSL 3.0 version thus older releases are not affected by the issue. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).📖 Read
via "National Vulnerability Database".
‼ CVE-2022-1434 ‼
📖 Read
via "National Vulnerability Database".
The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key. This makes the MAC key trivially predictable. An attacker could exploit this issue by performing a man-in-the-middle attack to modify data being sent from one endpoint to an OpenSSL 3.0 recipient such that the modified data would still pass the MAC integrity check. Note that data sent from an OpenSSL 3.0 endpoint to a non-OpenSSL 3.0 endpoint will always be rejected by the recipient and the connection will fail at that point. Many application protocols require data to be sent from the client to the server first. Therefore, in such a case, only an OpenSSL 3.0 server would be impacted when talking to a non-OpenSSL 3.0 client. If both endpoints are OpenSSL 3.0 then the attacker could modify data being sent in both directions. In this case both clients and servers could be affected, regardless of the application protocol. Note that in the absence of an attacker this bug means that an OpenSSL 3.0 endpoint communicating with a non-OpenSSL 3.0 endpoint will fail to complete the handshake when using this ciphersuite. The confidentiality of data is not impacted by this issue, i.e. an attacker cannot decrypt data that has been encrypted using this ciphersuite - they can only modify it. In order for this attack to work both endpoints must legitimately negotiate the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in OpenSSL 3.0, and is not available within the default provider or the default ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the following must have occurred: 1) OpenSSL must have been compiled with the (non-default) compile time option enable-weak-ssl-ciphers 2) OpenSSL must have had the legacy provider explicitly loaded (either through application code or via configuration) 3) The ciphersuite must have been explicitly added to the ciphersuite list 4) The libssl security level must have been set to 0 (default is 1) 5) A version of SSL/TLS below TLSv1.3 must have been negotiated 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any others that both endpoints have in common Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).📖 Read
via "National Vulnerability Database".
‼ CVE-2022-1343 ‼
📖 Read
via "National Vulnerability Database".
The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. In the case where the (non-default) flag OCSP_NOCHECKS is used then the response will be positive (meaning a successful verification) even in the case where the response signing certificate fails to verify. It is anticipated that most users of `OCSP_basic_verify` will not use the OCSP_NOCHECKS flag. In this case the `OCSP_basic_verify` function will return a negative value (indicating a fatal error) in the case of a certificate verification failure. The normal expected return value in this case would be 0. This issue also impacts the command line OpenSSL "ocsp" application. When verifying an ocsp response with the "-no_cert_checks" option the command line application will report that the verification is successful even though it has in fact failed. In this case the incorrect successful response will also be accompanied by error messages showing the failure and contradicting the apparently successful result. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2).📖 Read
via "National Vulnerability Database".
‼ CVE-2021-22573 ‼
📖 Read
via "National Vulnerability Database".
The vulnerability is that IDToken verifier does not verify if token is properly signed. Signature verification makes sure that the token's payload comes from valid provider, not from someone else. An attacker can provide a compromised token with custom payload. The token will pass the validation on the client side. We recommend upgrading to version 1.33.3 or above📖 Read
via "National Vulnerability Database".
🕴 REvil Revival: Are Ransomware Gangs Ever Really Gone? 🕴
📖 Read
via "Dark Reading".
The infamous ransomware group appears to be back from the dead — maybe — and using the old brand, but experts question whether a reconstituted gang will have much success.📖 Read
via "Dark Reading".
Darkreading
REvil Revival: Are Ransomware Gangs Ever Really Gone?
The infamous ransomware group appears to be back from the dead — maybe — and using the old brand, but experts question whether a reconstituted gang will have much success.
🕴 Unpatched DNS-Poisoning Bug Affects Millions of Devices, Stumps Researchers 🕴
📖 Read
via "Dark Reading".
The security vulnerability puts wide swaths of industrial networks and IoT devices at risk of compromise, researchers warn.📖 Read
via "Dark Reading".
Darkreading
Unpatched DNS-Poisoning Bug Affects Millions of Devices, Stumps Researchers
The security vulnerability puts wide swaths of industrial networks and IoT devices at risk of compromise, researchers warn.
‼ CVE-2022-28585 ‼
📖 Read
via "National Vulnerability Database".
EmpireCMS 7.5 has a SQL injection vulnerability in AdClass.php📖 Read
via "National Vulnerability Database".
‼ CVE-2021-46440 ‼
📖 Read
via "National Vulnerability Database".
Storing passwords in a recoverable format in the DOCUMENTATION plugin component of Strapi before 3.6.9 and 4.x before 4.1.5 allows an attacker to access a victim's HTTP request, get the victim's cookie, perform a base64 decode on the victim's cookie, and obtain a cleartext password, leading to getting API documentation for further API attacks.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-28588 ‼
📖 Read
via "National Vulnerability Database".
In SpringBootMovie <=1.2 when adding movie names, malicious code can be stored because there are no filtering parameters, resulting in stored XSS.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-22368 ‼
📖 Read
via "National Vulnerability Database".
IBM Spectrum Scale 5.1.0 through 5.1.3.0 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 221012.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-1331 ‼
📖 Read
via "National Vulnerability Database".
In four instances DMARS (All versions prior to v2.1.10.24) does not properly restrict references of XML external entities while processing specific project files, which may allow unauthorized information disclosure.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-28599 ‼
📖 Read
via "National Vulnerability Database".
A stored cross-site scripting (XSS) vulnerability exists in FUEL-CMS 1.5.1 that allows an authenticated user to upload a malicious .pdf file which acts as a stored XSS payload. If this stored XSS payload is triggered by an administrator it will trigger a XSS attack.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-29001 ‼
📖 Read
via "National Vulnerability Database".
In SpringBootMovie <=1.2, the uploaded file suffix parameter is not filtered, resulting in arbitrary file upload vulnerability📖 Read
via "National Vulnerability Database".
‼ CVE-2021-29854 ‼
📖 Read
via "National Vulnerability Database".
IBM Maximo Asset Management 7.6.1.1 and 7.6.1.2 is vulnerable to HTTP header injection, caused by improper validation of input by the HOST headers. By sending a specially crafted HTTP request, a remote attacker could exploit this vulnerability to inject HTTP HOST header, which will allow the attacker to conduct various attacks against the vulnerable system, including cross-site scripting, cache poisoning or session hijacking. IBM X-Force ID: 205680.📖 Read
via "National Vulnerability Database".
🕴 SolarWinds Attackers Gear Up for Typosquatting Attacks 🕴
📖 Read
via "Dark Reading".
The same infrastructure traced back to Russian-speaking threat group Nobelium is being used to set up misspelled domain names, presaging impersonation attacks bent on credential harvesting, analysts say.📖 Read
via "Dark Reading".
Darkreading
SolarWinds Attackers Gear Up for Typosquatting Attacks
The same infrastructure traced back to Russian-speaking threat group Nobelium is being used to set up misspelled domain names, presaging impersonation attacks bent on credential harvesting, analysts say.
🕴 Syxsense Enterprise Unifies Endpoint Security and IT Management for Real-Time Vulnerability Monitoring and Remediation 🕴
📖 Read
via "Dark Reading".
IT Teams can now manage, detect, and secure all endpoints with 100% visibility across desktop, laptop, server, and mobile devices.📖 Read
via "Dark Reading".
Dark Reading
Remote Workforce recent news | Dark Reading
Explore the latest news and expert commentary on Remote Workforce, brought to you by the editors of Dark Reading
🕴 API Security Company Traceable AI Lands $60 Million Series B 🕴
📖 Read
via "Dark Reading".
Latest round led by IVP values the company at $450 million.📖 Read
via "Dark Reading".
Darkreading
API Security Company Traceable AI Lands $60 Million Series B
Latest round led by IVP values the company at $450 million.
‼ CVE-2022-20094 ‼
📖 Read
via "National Vulnerability Database".
In imgsensor, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06479763; Issue ID: ALPS06479734.📖 Read
via "National Vulnerability Database".
‼ CVE-2021-27411 ‼
📖 Read
via "National Vulnerability Database".
Micrium OS Versions 5.10.1 and prior are vulnerable to integer wrap-around in functions Mem_DynPoolCreate, Mem_DynPoolCreateHW and Mem_PoolCreate. This unverified memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as very small blocks of memory being allocated instead of very large ones.📖 Read
via "National Vulnerability Database".
‼ CVE-2022-20109 ‼
📖 Read
via "National Vulnerability Database".
In ion, there is a possible use after free due to improper update of reference count. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS06399915; Issue ID: ALPS06399915.📖 Read
via "National Vulnerability Database".
‼ CVE-2021-27427 ‼
📖 Read
via "National Vulnerability Database".
RIOT OS version 2020.01.1 is vulnerable to integer wrap-around in its implementation of calloc function, which can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution.📖 Read
via "National Vulnerability Database".