[
https://issues.apache.org/jira/browse/DBCP-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052020#comment-17052020
]
Frank Gasdorf commented on DBCP-562:
------------------------------------
Read this discussion and I guess the Wrapper-Approach for JMX Beans might also
work. Since (as stated in DBCP-448) its a read-only interface the Wrapper might
delegate everything except password. {{getPassword()}} could be overwritten and
return always "****" in this case (only for registered MBean)
I'll try this and refactor the pull request
> Password should not be exposed via JMXBean
> ------------------------------------------
>
> Key: DBCP-562
> URL: https://issues.apache.org/jira/browse/DBCP-562
> Project: Commons DBCP
> Issue Type: Bug
> Affects Versions: 2.5.0, 2.7.0
> Reporter: Frank Gasdorf
> Priority: Critical
> Labels: security
> Time Spent: 40m
> Remaining Estimate: 0h
>
> if a BasicDataSource is created with jmxName set, password property is
> exposed/exported via jmx and is visible for everybody who is connected to jmx
> port.
>
> Expectation : Do not export it via BasicDataSourceMXBean Interface
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
