The put command functionality in beanstalkd 1.4.5 and earlier allows remote attackers to execute arbitrary Beanstalk commands via the body in a job that is too big, which is not properly handled by the dispatch_cmd function in prot.c.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Beanstalkd | Wildbit | * | 1.4.5 (including) |
Beanstalkd | Wildbit | 0.5 (including) | 0.5 (including) |
Beanstalkd | Wildbit | 0.6 (including) | 0.6 (including) |
Beanstalkd | Wildbit | 0.7 (including) | 0.7 (including) |
Beanstalkd | Wildbit | 0.8 (including) | 0.8 (including) |
Beanstalkd | Wildbit | 0.9 (including) | 0.9 (including) |
Beanstalkd | Wildbit | 0.10 (including) | 0.10 (including) |
Beanstalkd | Wildbit | 1.0 (including) | 1.0 (including) |
Beanstalkd | Wildbit | 1.1 (including) | 1.1 (including) |
Beanstalkd | Wildbit | 1.2 (including) | 1.2 (including) |
Beanstalkd | Wildbit | 1.3 (including) | 1.3 (including) |
Beanstalkd | Wildbit | 1.4 (including) | 1.4 (including) |
Beanstalkd | Wildbit | 1.4.1 (including) | 1.4.1 (including) |
Beanstalkd | Wildbit | 1.4.2 (including) | 1.4.2 (including) |
Beanstalkd | Wildbit | 1.4.3 (including) | 1.4.3 (including) |
Beanstalkd | Wildbit | 1.4.4 (including) | 1.4.4 (including) |
Beanstalkd | Ubuntu | lucid | * |
Beanstalkd | Ubuntu | upstream | * |