Sander Meijering

**Name of the Vulnerable Software and Affected Versions** Microsoft Dynamics 365 (Online) (affected versions not specified) **Description** A server-side request forgery (SSRF) allows an unauthorized attacker to perform spoofing over a network. SSRF is a flaw where an attacker can force a server-side application to make HTTP requests to an arbitrary domain of the attacker's choosing. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** PeopleSoft Enterprise PeopleTools versions 8.58 through 8.59 **Description** The issue is related to insufficient input validation in the Process Scheduler component. It allows an unauthenticated attacker with network access via HTTP to compromise PeopleSoft Enterprise PeopleTools, requiring human interaction from a person other than the attacker. Successful attacks can result in unauthorized update, insert, or delete access to some of PeopleSoft Enterprise PeopleTools' accessible data, as well as unauthorized read access to a subset of PeopleSoft Enterprise PeopleTools' accessible data. Attacks may significantly impact additional products. **Recommendations** For versions 8.58 and 8.59, update to a version that includes the fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Oracle WebLogic Server versions 12.1.3.0.0 through 14.1.1.0.0 **Description** The issue is related to the Web Container component of Oracle WebLogic Server, which has a vulnerability that allows an unauthenticated attacker with network access via HTTP to compromise the server. This can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. The vulnerability is easily exploitable and can be triggered by a specially crafted HTTP request. **Recommendations** For versions 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0, and 14.1.1.0.0, update to a version that includes the fix for this issue. At the moment, there is no information about a newer version that contains a fix for this vulnerability.