0day.today - Biggest Exploit Database in the World.
- We use one main domain: http://0day.today
- Most of the materials is completely FREE
- If you want to purchase the exploit / get V.I.P. access or pay for any other service,
you need to buy or earn
GOLD
Administration of this site uses the official contacts. Beware of impostors!
We DO NOT use Telegram or any messengers / social networks!Please, beware of scammers!
- Read the [ agreement ]
- Read the [ Submit ] rules
- Visit the [ faq ] page
- [ Register ] profile
- Get [ GOLD ]
- If you want to [ sell ]
- If you want to [ buy ]
- If you lost [ Account ]
- Any questions [ admin@0day.today ]
- Authorisation page
- Registration page
- Restore account page
- FAQ page
- Contacts page
- Publishing rules
- Agreement page
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
Contact us
You can contact us by:
Mail:
Facebook:
Twitter:
Telegram:
We DO NOT use Telegram or any messengers / social networks!
snircd <= 1.3.4 (send_user_mode) Denial of Service Vulnerability
[================================================================ snircd <= 1.3.4 (send_user_mode) Denial of Service Vulnerability ================================================================ Affected software ----------------- ircu (upto and including 2.10.12.12) snircd (upto and including 1.3.4) and many other ircu derivatives Vulnerability details --------------------- send_user_mode in s_user.c does not check that the argument after a +r mode is present, if it is not than the NULL sentinel may be missed, causing the function to iterate over the boundary of the array. One possible exploit: /mode nickname i i i i i i i i i i i i i i i r r r r s This won't work if there's another NULL directly after the first from the previous parsed command, if this is the case one can just append more modes or send some other junk to the ircd. Resolution ---------- Upgrade to the very latest version of ircu/snircd. Disclosure timeline ------------------- 2008-03-15: Vulnerability discovered by QuakeNet and reported to Undernet. 2008-03-15: Patches released. 2008-03-17: Patches applied to public servers. 2008-03-24: Public disclosure. -- # 0day.today [2024-12-24] #