December 2012 - esb-issues - Jboss List Archives

[JBoss JIRA] (JBESB-3890) jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3890?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3890: ---------------------------------- Fix Version/s: 4.12 (was: 4.11 CP2) > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370 > --------------------------------------------------------- > > Key: JBESB-3890 > URL: https://issues.jboss.org/browse/JBESB-3890 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.11 > Reporter: David Jorm > Assignee: Tom Cunningham > Fix For: 4.12 > > > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370. We are shipping JRuby 1.6.5.1. The upstream Ruby language has replaced the vulnerable Murmur hash function / algorithm implementation with the SipHash-2-4 implementation: > http://www.ruby-lang.org/en/news/2012/11/09/ruby19-hashdos-cve-2012-5371/ > An upstream fix is not yet available for JRuby. Once an upstream fix is available, we should incorporate it into a future release via a component upgrade. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3890) jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370

by Tom Cunningham (JIRA)

Tom Cunningham created JBESB-3890: ------------------------------------- Summary: jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370 Key: JBESB-3890 URL: https://issues.jboss.org/browse/JBESB-3890 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 4.11 Reporter: David Jorm Assignee: Tom Cunningham Fix For: 4.11 CP2 jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370. We are shipping JRuby 1.6.5.1. The upstream Ruby language has replaced the vulnerable Murmur hash function / algorithm implementation with the SipHash-2-4 implementation: http://www.ruby-lang.org/en/news/2012/11/09/ruby19-hashdos-cve-2012-5371/ An upstream fix is not yet available for JRuby. Once an upstream fix is available, we should incorporate it into a future release via a component upgrade. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3884) jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3884?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3884: ---------------------------------- Fix Version/s: 4.11 CP2 > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370 > --------------------------------------------------------- > > Key: JBESB-3884 > URL: https://issues.jboss.org/browse/JBESB-3884 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.11 > Reporter: David Jorm > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370. We are shipping JRuby 1.6.5.1. The upstream Ruby language has replaced the vulnerable Murmur hash function / algorithm implementation with the SipHash-2-4 implementation: > http://www.ruby-lang.org/en/news/2012/11/09/ruby19-hashdos-cve-2012-5371/ > An upstream fix is not yet available for JRuby. Once an upstream fix is available, we should incorporate it into a future release via a component upgrade. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3884) jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3884?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3884. --------------------------------- > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370 > --------------------------------------------------------- > > Key: JBESB-3884 > URL: https://issues.jboss.org/browse/JBESB-3884 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.11 > Reporter: David Jorm > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370. We are shipping JRuby 1.6.5.1. The upstream Ruby language has replaced the vulnerable Murmur hash function / algorithm implementation with the SipHash-2-4 implementation: > http://www.ruby-lang.org/en/news/2012/11/09/ruby19-hashdos-cve-2012-5371/ > An upstream fix is not yet available for JRuby. Once an upstream fix is available, we should incorporate it into a future release via a component upgrade. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3884) jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3884?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3884. ----------------------------------- Resolution: Done Upgraded to jruby 1.7.1 > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370 > --------------------------------------------------------- > > Key: JBESB-3884 > URL: https://issues.jboss.org/browse/JBESB-3884 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.11 > Reporter: David Jorm > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > jruby.jar as shipped with JBoss ESB exposes CVE-2012-5370. We are shipping JRuby 1.6.5.1. The upstream Ruby language has replaced the vulnerable Murmur hash function / algorithm implementation with the SipHash-2-4 implementation: > http://www.ruby-lang.org/en/news/2012/11/09/ruby19-hashdos-cve-2012-5371/ > An upstream fix is not yet available for JRuby. Once an upstream fix is available, we should incorporate it into a future release via a component upgrade. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3889) Shorten table name length on jUDDI signature table / change orm mapping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3889?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated JBESB-3889: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=887296 > Shorten table name length on jUDDI signature table / change orm mapping > ----------------------------------------------------------------------- > > Key: JBESB-3889 > URL: https://issues.jboss.org/browse/JBESB-3889 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > length of table name should be max 30 characters long: > Wrong line: > create table j3_signature_transform_data_value > Full exception log: > 2012-12-14 10:15:17,518 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.esb:service=JUDDIDatabaseInitializer state=Create mode=Manual requiredState=Installed > java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3889) Shorten table name length on jUDDI signature table / change orm mapping

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBESB-3889?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBESB-3889: ------------------------------------------------ tcunning(a)redhat.com changed the Status of [bug 887296|https://bugzilla.redhat.com/show_bug.cgi?id=887296] from ON_DEV to MODIFIED > Shorten table name length on jUDDI signature table / change orm mapping > ----------------------------------------------------------------------- > > Key: JBESB-3889 > URL: https://issues.jboss.org/browse/JBESB-3889 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > length of table name should be max 30 characters long: > Wrong line: > create table j3_signature_transform_data_value > Full exception log: > 2012-12-14 10:15:17,518 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.esb:service=JUDDIDatabaseInitializer state=Create mode=Manual requiredState=Installed > java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3889) Shorten table name length on jUDDI signature table / change orm mapping

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3889?page=com.atlassian.jira.plugin... ] Tom Cunningham resolved JBESB-3889. ----------------------------------- Assignee: Tom Cunningham Resolution: Done > Shorten table name length on jUDDI signature table / change orm mapping > ----------------------------------------------------------------------- > > Key: JBESB-3889 > URL: https://issues.jboss.org/browse/JBESB-3889 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > length of table name should be max 30 characters long: > Wrong line: > create table j3_signature_transform_data_value > Full exception log: > 2012-12-14 10:15:17,518 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.esb:service=JUDDIDatabaseInitializer state=Create mode=Manual requiredState=Installed > java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3889) Shorten table name length on jUDDI signature table / change orm mapping

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3889?page=com.atlassian.jira.plugin... ] Tom Cunningham closed JBESB-3889. --------------------------------- > Shorten table name length on jUDDI signature table / change orm mapping > ----------------------------------------------------------------------- > > Key: JBESB-3889 > URL: https://issues.jboss.org/browse/JBESB-3889 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Assignee: Tom Cunningham > Fix For: 4.11 CP2 > > > length of table name should be max 30 characters long: > Wrong line: > create table j3_signature_transform_data_value > Full exception log: > 2012-12-14 10:15:17,518 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.esb:service=JUDDIDatabaseInitializer state=Create mode=Manual requiredState=Installed > java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBESB-3889) Shorten table name length on jUDDI signature table / change orm mapping

by Tom Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBESB-3889?page=com.atlassian.jira.plugin... ] Tom Cunningham updated JBESB-3889: ---------------------------------- Affects Version/s: 4.11 CP2 > Shorten table name length on jUDDI signature table / change orm mapping > ----------------------------------------------------------------------- > > Key: JBESB-3889 > URL: https://issues.jboss.org/browse/JBESB-3889 > Project: JBoss ESB > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Registry and Repository > Affects Versions: 4.11 CP2 > Reporter: Tom Cunningham > Fix For: 4.11 CP2 > > > length of table name should be max 30 characters long: > Wrong line: > create table j3_signature_transform_data_value > Full exception log: > 2012-12-14 10:15:17,518 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error installing to Start: name=jboss.esb:service=JUDDIDatabaseInitializer state=Create mode=Manual requiredState=Installed > java.sql.SQLSyntaxErrorException: ORA-00972: identifier is too long -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues December 2012