
Sheridan Junior High School
Strong
None
Strong
None
Strong
Old Mutual Limited is a premium pan-African financial services group that offers a broad spectrum of financial solutions to retail and corporate customers across key markets in 14 countries. We have been helping our customers achieve their lifetime financial goals for over 170 years by investing their funds in ways that create positive futures for them, their families, their communities and broader society. In this way, we significantly contribute to improving the lives of our customers and their communities while ensuring a sustainable future for our business. We employ more than 30 000 people and operate in 14 countries across two regions Africa (South Africa, Namibia, Botswana, Zimbabwe, Kenya, Malawi, Tanzania, Nigeria, Ghana, Uganda, Rwanda, South Sudan and eSwatini) as well as Asia (China) So why work here? We believe you can shape the future with us โ a future where we build a better Africa together. Thatโs why weโre committed to creating opportunities that will give you an edge on the rest. Once youโre part of our team, you will have access to the best breed of advice, tools and frameworks that will equip you to be your exceptional best. #MomentsThatMatter
Security & Compliance Standards Overview
No incidents recorded for Sheridan Junior High School in 2025.
No incidents recorded for Old Mutual South Africa in 2025.
Sheridan Junior High School cyber incidents detection timeline including parent company and subsidiaries
Old Mutual South Africa cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
FreshRSS is a free, self-hostable RSS aggregator. Versions 1.26.3 and below do not sanitize certain event handler attributes in feed content, so by finding a page that renders feed entries without CSP, it is possible to execute an XSS payload. The Allow API access authentication setting needs to be enabled by the instance administrator beforehand for the attack to work as it relies on api/query.php. An account takeover is possible by sending a change password request via the XSS payload / setting UserJS for persistence / stealing the autofill password / displaying a phishing page with a spoofed URL using history.replaceState() If the victim is an administrator, the attacker can also perform administrative actions. This issue is fixed in version 1.27.0.
go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.6 and below, go-f3 panics when it validates a "poison" messages causing Filecoin nodes consuming F3 messages to become vulnerable. A "poison" message can can cause integer overflow in the signer index validation, which can cause the whole node to crash. These malicious messages aren't self-propagating since the bug is in the validator. An attacker needs to directly send the message to all targets. This issue is fixed in version 0.8.7.
go-f3 is a Golang implementation of Fast Finality for Filecoin (F3). In versions 0.8.8 and below, go-f3's justification verification caching mechanism has a vulnerability where verification results are cached without properly considering the context of the message. An attacker can bypass justification verification by submitting a valid message with a correct justification and then reusing the same cached justification in contexts where it would normally be invalid. This occurs because the cached verification does not properly validate the relationship between the justification and the specific message context it's being used with. This issue is fixed in version 0.8.9.
mkdocs-include-markdown-plugin is an Mkdocs Markdown includer plugin. In versions 7.1.7 and below, there is a vulnerability where unvalidated input can collide with substitution placeholders. This issue is fixed in version 7.1.8.
go-mail is a comprehensive library for sending mails with Go. In versions 0.7.0 and below, due to incorrect handling of the mail.Address values when a sender- or recipient address is passed to the corresponding MAIL FROM or RCPT TO commands of the SMTP client, there is a possibility of wrong address routing or even ESMTP parameter smuggling. For successful exploitation, it is required that the user's code allows for arbitrary mail address input (i. e. through a web form or similar). If only static mail addresses are used (i. e. in a config file) and the mail addresses in use do not consist of quoted local parts, this should not affect users. This issue is fixed in version 0.7.1