Fixes are available
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
APAR status
Closed as program error.
Error description
If the argument to the EXSLT date:year or date:leap-year does not have the lexical form of an xs:dateTime, xs:date, xs:gYear or xs:gYearMonth value, the result of the function should be NaN. However, the processor is only checking whether the leading characters in the argument are one of the required lexical forms - if there are incorrect trailing characters, the processor is ignoring them. This causes the processor to incorrectly accept invalid data as input to these functions.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of the XML API for IBM WebSphere * * Application Server V8.0 * **************************************************************** * PROBLEM DESCRIPTION: The argument to the EXSLT date:year * * or date:leap-year function is not * * syntactically correct, the result * * should be NaN. However, if the * * leading characters in the argument * * have the lexical form of an * * xs:dateTime, xs:date, xs:gYear or * * xs:gYearMonth value, the processor * * returns the result of invoking the * * function on just that leading portion * * of the argument instead of returning * * NaN. * **************************************************************** * RECOMMENDATION: Install a fix pack that contains this APAR. * **************************************************************** When the processor parses the argument to one of the EXSLT date:year or date:leap-year extension functions, it uses a method that is able to parse the value incrementally. That is, it can parse the leading portion of the value to verify that it adheres to a particular format, then parse the next portion to verify that it adheres to the same or another format, and so on. However, in the case of these functions, there can only be one value. The processor was not checking whether there were any trailing characters after parsing the leading portion of the string.
Problem conclusion
The problem was fixed by having the processor check whether any trailing characters in the argument to date:year or date:leap-year remain after parsing the leading portion of the argument. If there are any such left over characters, the processor returns NaN as the result of the function instead of ignoring the trailing characters. The fix for this APAR is currently targeted for inclusion in fix pack 8.0.0.1. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM41714
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
800
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-06-15
Closed date
2011-06-15
Last modified date
2011-06-28
APAR is sysrouted FROM one or more of the following:
PM32381
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800
Applicable component levels
R800 PSY
Document Information
Modified date:
27 October 2021