[omniORB] omniORB and omniORBpy 4.3.5 released with security fixes
Thomas Braun
thomas.braun at byte-physics.de
Thu Nov 12 20:32:20 UTC 2026
Am Donnerstag, dem 12.11.2026 um 16:04 +0000 schrieb Duncan Grisby:
> (Replying to two messages at once)
>
> On Thu, 2026-11-12 at 16:18 +0100, Thomas Braun via omniORB-list
> wrote:
>
>
> > thanks for the release and the info. Are you doing CVEs? I want to
> > ping downstream packagers and that would help getting it quickly
> > integrated.
>
> I was not intending to do so, but it could probably be done. I'm not
> sure who would allocate a CVE number for omniORB, though.
I've never done the process.
But what I read so far is:
- You need to find a CVE Numbering Authority (CNA) which is responsible
for your software. If it would be on github/gitlab they would be that.
I can't think of any CNA which would be responsible, so you can use
MITRE (CNA of Last Resort). Redhat also runs a CNA of last resort.
- If you choose MITRE, go to
https://mitre.github.io/mitre-cve-roles/CNA-LR/ and fill out the forms.
- Wait a couple of days
- More forms (?!)
- Done
> > Is the bugfix in revision r6833 only?
>
> Yes.
>
Nice!
> One issue had actually already been fixed in the 4_4 development /
> beta
> branch; the other one was fixed in revision r6835.
>
> > And is the bug present in earlier versions as well? From my playing
> > around the patch applies onto 4.2.5 as well.
>
> Yes, it is in older versions, and the same fix will work on 4.2.x,
> but considering that 4.3.0 was released in January 2022, I would
> really consider 4.2.x out of support.
I hear you. But we use 4.2.1 for the current tango LTS release we did
in 2020 and which is still around, so I'll do the patching.
Thanks!
--
() byte physics e.K.
Züllsdorfer Str. 39
06925 Annaburg
Germany
Web: www.byte-physics.de
Telephone: +49 (0)35385/339233
USt-IdNr: DE276717536
More information about the omniORB-list
mailing list