JDK-7024767 : Some unquoted special character are allowed by X500Principal constructor
- Type: Bug
- Component: security-libs
- Sub-Component: java.security
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- OS: linux
- CPU: x86
- Submitted: 2011-03-04
- Updated: 2011-08-30
- Resolved: 2011-08-30
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 |
|---|
8Resolved  |
Related Reports
|
Duplicate :
|
Description
BNF RFC 2253 introduces concewpt of special characters that can occur in the attribute value only if they are escaped by "\".
Special characters are following: "," / "=" / "+" / "<" / ">" / "#" / ";"
However following constructor calls:
new X500Principal("CN=<");
new X500Principal("CN=>");
new X500Principal("CN==");
do not cause IAE
Note, that subsequent gerName() call returns escaped special characters.
For example, (new X500Principal("CN==")).getName() returns "CN=\\="
Comments
|