git: bc550c727973 - main - security/vuxml: Document ejabberd vulnerability
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sat, 19 Apr 2025 09:09:58 UTC
The branch main has been updated by ashish:
URL: https://cgit.FreeBSD.org/ports/commit/?id=bc550c72797395b13e04c381ed2f6bdd9fb4442d
commit bc550c72797395b13e04c381ed2f6bdd9fb4442d
Author: Ashish SHUKLA <ashish@FreeBSD.org>
AuthorDate: 2025-04-19 09:07:57 +0000
Commit: Ashish SHUKLA <ashish@FreeBSD.org>
CommitDate: 2025-04-19 09:08:51 +0000
security/vuxml: Document ejabberd vulnerability
---
security/vuxml/vuln/2025.xml | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/security/vuxml/vuln/2025.xml b/security/vuxml/vuln/2025.xml
index 404b7d9a4afc..90b4b50e1a05 100644
--- a/security/vuxml/vuln/2025.xml
+++ b/security/vuxml/vuln/2025.xml
@@ -1,3 +1,34 @@
+ <vuln vid="1b8d502e-1cfd-11f0-944d-901b0e9408dc">
+ <topic>ejabberd -- mod_muc_occupantid: Fix handling multiple occupant-id</topic>
+ <affects>
+ <package>
+ <name>ejabberd</name>
+ <range><lt>25.04</lt></range>
+ </package>
+ </affects>
+ <description>
+ <body xmlns="http://www.w3.org/1999/xhtml">
+ <p>ejabberd team reports:</p>
+ <blockquote cite="https://www.process-one.net/blog/ejabberd-25-04/#occupantid">
+ <p>Fixed issue with handling of user provided occupant-id in
+ messages and presences sent to muc room. Server was
+ replacing just first instance of occupant-id with its own
+ version, leaving other ones untouched. That would mean that
+ depending on order in which clients send occupant-id, they
+ could see value provided by sender, and that could be used
+ to spoof as different sender.</p>
+ </blockquote>
+ </body>
+ </description>
+ <references>
+ <url>https://www.process-one.net/blog/ejabberd-25-04/#occupantid</url>
+ </references>
+ <dates>
+ <discovery>2025-04-16</discovery>
+ <entry>2025-04-19</entry>
+ </dates>
+ </vuln>
+
<vuln vid="bf5d29ea-1a93-11f0-8cb5-a8a1599412c6">
<topic>chromium -- multiple security fixes</topic>
<affects>