You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Sergey Beryozkin (Resolved) (JIRA)" <ji...@apache.org> on 2011/10/21 17:28:32 UTC
[jira] [Resolved] (CXF-3873) Detail exceptions in
JAASLoginInInterceptor (patch)
[ https://issues.apache.org/jira/browse/CXF-3873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Beryozkin resolved CXF-3873.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.5
2.4.4
patch has been applied, thanks
> Detail exceptions in JAASLoginInInterceptor (patch)
> ---------------------------------------------------
>
> Key: CXF-3873
> URL: https://issues.apache.org/jira/browse/CXF-3873
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Affects Versions: 2.5
> Environment: Windows
> Reporter: Andrei Shakirin
> Fix For: 2.4.4, 2.5
>
> Attachments: JAASLoginInterceptor-patch.java, SAAJOutInterceptor-patch.java
>
>
> Hi,
> I find one thing in JAASLoginInInterceptor a little bit dangerous from security perspective - exception handling.
> JAASLoginInInterceptor throws different exceptions with detail error messages in cases:
> - if user/password are not defined (SecurityException: NO_USER_PASSWORD)
> - and if authentication is failed (AuthenticationException: "Unauthorized : " + ex.getMessage())
> It is very practical for the development, but can give some advices to malicious application.
> I will prefere to throw generic security violation exception for both cases.
> Patch is attached
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira