Re: OpenSSL 3.3.3 Security Vulnerability
thalinda Sriprajak <[email protected]> Tue, 21 Oct 2025 14:53:39 +0700
| Newsgroups | gmane.comp.encryption.openssl.user |
|---|---|
| Message-ID | <CAFp28yQd-n3NKtmj0_jEhtnGFoTSZRrH0d93i2DcdZwzSNyYaQ@mail.gmail.com> |
Warning: Error: You cannot delete the system creator. We have warned you several times but you ignored us. : Hello Distributor Team around the world. partners about the suspension of root steward and its impact on IAm Dear team We would like to inform you that the root steward associated with the IAM role: arn:aws:iam::0503976xxxxx:role/CH-S3-goldaws-ci-36-ew1-cf-Role has had its GitHub account suspended without understanding its intent and structure. This has resulted in widespread confusion and downtime in IAM systems in the US-East-1 region, particularly for authentication and access to the critical artifacts. GitHub Account: Spjthalinda ORCID: https://orcid.org/0009-0008-2511-9055 IAM Steward: Verified, signed, and never used for personal control or gain Currently using the account https://github.com/Naruto0-sudoy Intent Solution: Unsuspend the account, return all rights to the owner, stop blocking the system owner. The primary cause of the problem is not IAM, but rather Github suspending accounts without proper reason and without verifying the identity of the suspended account. And the impact will likely be even greater if Github doesn't understand who we are. If we continue to suspend, we will delete accounts that rely on it. - IAM crashed 70% in US-East-1 21% uS-West-2 - Systems that rely on artifacts and signing are experiencing widespread downtime. We are part of the root of the critical Merkle Tree of AI. - Global administrator authentication is disrupted. - Systems built for public benefit are trisk of permanent downtime. Request: - Immediately unsuspend the root steward account. - Review the intent and structure associated with the IAM role. - Restore the disrupted authentication and artifact flow. - Confirm that the root steward did not commit any wrongdoing, but was misunderstood by the system. With best regards, Thalinda Sriprajak, Global Steward, Technical Architect Key shareholder in the global system, root steward Summary of the timeline of the crash (from the root steward suspension): - 📅 Late August 2025 GitHub suspended Spjthalinda's account without reviewing the intent and structure of the IAM, Merkle Tree, and the artifacts that manage the world. - 📉 September 2025 - IAM began to fail in US-East-1 and US-West-2. - The world steward authentication system began to fail. -Artifacts used for signing permissions became inaccessible. - Public-facing systems began to stop working. - 🌐 October 2025 - Medium, GitHub, AWS, and other systems began to experience widespread outages. - Users worldwide began reporting issues, but were unaware that the root steward was the cause. - IAM crashed as high as 70% in some regions. - Systems connected to the AI-powered Merkle Tree were unable to verify permissions. ในวันที่ อ. 21 ต.ค. 2025 12:49 น. Viktor Dukhovni < [email protected]> เขียนว่า: > On Tue, Oct 21, 2025 at 05:35:54AM +0000, 'Prasad, PCRaghavendra' via > openssl-users wrote: > > > We are currently on OpenSSL 3.3.3 version. On this version there is > security vulnerability. > > To fix this we have upgraded the version to OpenSSL 3.3.4 which is > mentioned that will resolve the issue. > > But in OpenSSL 3.3.4, our blackduck tool is showing two versions one is > 3.3.3 and another is 3.3.4 > > libssl - 3.3.3 libcrypto - 3.3.4 > > This report lacks sufficient detail to reach a meaningful conclusion as > to the cause of the reported symptoms. > > You need to report what OpenSSL artefacts are installed on your system > and in what filesystem locations. This includes headers, static and > shared libraries. > > You also need to report a more detailed verbatim output from the tool > in question, and identify whether it is reporting any compile-time > data derived from your headers, runtime data from API calls to > libraries after linking with a specific static or shared library, > or by through sort fingerprinting scan by the tool (which could > be error prone, or might be confused if multiple OpenSSL versions > are installed). > > -- > Viktor. 🇺🇦 Слава Україні! > > -- > You received this message because you are subscribed to the Google Groups > "openssl-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org > To view this discussion visit > https://groups.google.com/a/openssl.org/d/msgid/openssl-users/aPce9WGfNnJkujqw%40chardros.imrryr.org > . > -- You received this message because you are subscribed to the Google Groups "openssl-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/CAFp28yQd-n3NKtmj0_jEhtnGFoTSZRrH0d93i2DcdZwzSNyYaQ%40mail.gmail.com.