Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-31650PUBLISHED: 2022-05-25In SoX 14.4.2, there is a floating-point exception in lsx_aiffstartwrite in aiff.c in libsox.a.
CVE-2022-31651PUBLISHED: 2022-05-25In SoX 14.4.2, there is an assertion failure in rate_init in rate.c in libsox.a.
CVE-2022-29256PUBLISHED: 2022-05-25
sharp is an application for Node.js image processing. Prior to version 0.30.5, there is a possible vulnerability in logic that is run only at `npm install` time when installing versions of `sharp` prior to the latest v0.30.5. If an attacker has the ability to set the value of the `PKG_CONFIG_PATH` e...
CVE-2022-26067PUBLISHED: 2022-05-25
An information disclosure vulnerability exists in the OAS Engine SecureTransferFiles functionality of Open Automation Software OAS Platform V16.00.0112. A specially-crafted series of network requests can lead to arbitrary file read. An attacker can send a sequence of requests to trigger this vulnera...
CVE-2022-26077PUBLISHED: 2022-05-25
A cleartext transmission of sensitive information vulnerability exists in the OAS Engine configuration communications functionality of Open Automation Software OAS Platform V16.00.0112. A targeted network sniffing attack can lead to a disclosure of sensitive information. An attacker can sniff networ...
User Rank: Apprentice
5/31/2018 | 2:32:44 AM
Thanks for the tip, appreciate it. Your article definitely helped me to understand the core concepts.
I'm most excited about the details your article touch based! I assume it doesn't come out of the box, it sounds like you are saying we'd need to write in the handlers ourselves.
Is there any other articles you would recommend to understand this better?
In the HANA migration guide, it is stated to run some consistency checks in FICO (see verbiage below).
I have run these, but I really don't know what I'm looking for - are we running just to make sure they run, running to validate numbers on the reports? Thoughts & guidance are appreciated. Thank you!
3.8 FI/CO: Performing Additional Consistency Checks
To ensure that the source system is consistent, user of Financial Accounting (FI) and Controlling (CO) need to perform some preparatory activities, among others additional consistency checks.
3.2 Product-Specific Preparations of the System Copy Guide, which is mentioned in Further Documentation [page 6].Caution Make sure that no customer data is changed in the meantime. Proceed as follows:
Procedure
1. FI: Run job SAPF190 to perform an additional consistency check. Choose AccountingFinancial AccountingGeneral ledgerPeriodic ProcessingClosingCheck/count. Then choose for○ classic FI: Reconciliation○ new general ledger: Reconciliation (New)
2. FI: You can further check consistency by running the jobs listed below:
○ RFUMSV00 (tax on sales/purchases)
○ RAGITT01 (asset history sheet)
○ RAZUGA01 (asset acquisitions)
○ RAABGA01 (fixed asset retirements)
3. CO: Run the report group 1SIP
Appreciate your effort for making such useful blogs and helping the community.
Thanks a heaps,
Irene Hynes