![]() |
January 16th, 2025 (6 months ago)
|
![]() |
Description: Impact
What kind of vulnerability is it? Who is impacted?
Remote code execution may be possible in web-accessible installations of Homarus in certain configurations.
Patches
Has the problem been patched? What versions should users upgrade to?
The issue has been patched in islandora/crayfish:4.1.0
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
The exploit requires making a request against the Homarus's /convert endpoint; therefore, the ability to exploit is much reduced if the microservice is not directly accessible from the Internet, so: Prevent general access from the Internet from hitting Homarus.
Configure auth in Crayfish to be more strongly required, such that requests with Authorization headers that do not validate are rejected before the problematic CLI interpolation occurs.
References
Are there any links users can visit to find out more?
XBOW-024-071
References
https://github.com/Islandora/Crayfish/security/advisories/GHSA-mm6v-68qp-f9fw
https://github.com/Islandora/Crayfish/commit/64cb4cec688928798cc40e6f0a0e863d7f69fd89
https://github.com/advisories/GHSA-mm6v-68qp-f9fw
January 15th, 2025 (6 months ago)
|
![]() |
Description: Prestige Maintenance USA has Fallen Victim to MEDUSA Ransomware
January 15th, 2025 (6 months ago)
|
![]() |
January 15th, 2025 (6 months ago)
|
![]() |
Description: It's an especially brazen form of malvertising, researchers say, striking at the heart of Google's business; the tech giant says it's aware of the issue and is working quickly to address the problem.
January 15th, 2025 (6 months ago)
|
![]() |
Description: SAP has fixed two critical vulnerabilities affecting NetWeaver web application server that could be exploited to escalate privileges and access restricted information. [...]
January 15th, 2025 (6 months ago)
|
![]() |
Description: Impact
A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.
The vulnerability allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. The victim email address must be known in order to exploit this vulnerability.
Patches
Sentry SaaS: The fix was deployed on Jan 14, 2025.
Self-Hosted Sentry: If only a single organization is allowed (SENTRY_SINGLE_ORGANIZATION = True), then no action is needed. Otherwise, users should upgrade to version 25.1.0 or higher.
Workarounds
No known workarounds.
References
https://github.com/getsentry/sentry/pull/83407
References
https://github.com/getsentry/sentry/security/advisories/GHSA-7pq6-v88g-wf3w
https://github.com/getsentry/sentry/pull/83407
https://github.com/getsentry/sentry/commit/6db508f7949d117c7dff748a3c82c3a272bf7cfd
https://github.com/advisories/GHSA-7pq6-v88g-wf3w
January 15th, 2025 (6 months ago)
|
![]() |
Description: In SP1’s STARK verifier, the prover provided chip_ordering is used to fetch the index of the chips that have preprocessed columns. Prior to v4.0.0, the validation that this chip_ordering correctly provides these indexes was missing. In v4.0.0, this was fixed by adding a check that the indexed chip’s name is equal to the name stored in the verifying key’s chip information.
In the recursive verifier, every verifier program is generated beforehand and later checked for correctness by requiring a merkle proof to the precomputed merkle root of valid verifier keys. Therefore, the recursive verifier and the on-chain verifier were not affected by this vulnerability.
This code was audited twice, once as a part of the audit by KALOS and once by Cantina for v1.0.0. This bug was found by the Succinct team during preparation of v4.0.0. Out of abundance of caution, we will be deprecating all previous versions and freeze the corresponding verifiers.
Furthermore, in the recursive verifier, the is_complete boolean flag is used to flag a proof of complete execution. Prior to v4.0.0, this flag was underconstrained in parts of our recursive verifier, such as the first layer of the recursion. In v4.0.0, this bug was fixed by adding appropriate calls to the assert_complete function, which constrains the correctness of the is_complete flag. This code was a part of the audit for v3.0.0. This bug affects the soundness of the Rust SDK for verifying compressed proofs, and the soundness of on-chain...
January 15th, 2025 (6 months ago)
|
![]() |
Description: Mr Hamza Targeted the Website of The Intelligence and Security Committee of the UK
January 15th, 2025 (6 months ago)
|
![]() |
Description: A Threat Actor Claims to have Leaked the Data of Jia Bo Sports
January 15th, 2025 (6 months ago)
|