Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inquiry - Java JMX Server Security Vulnerability #1595

Closed
josephmcasey opened this issue Mar 24, 2020 · 1 comment · Fixed by #1640
Closed

Inquiry - Java JMX Server Security Vulnerability #1595

josephmcasey opened this issue Mar 24, 2020 · 1 comment · Fixed by #1640
Assignees
Milestone

Comments

@josephmcasey
Copy link

…We just connect to the JMX RMI server using Java APIs, ask it to load this MLet file we supply containing a pointer to a JAR, which the server happily loads and will invoke methods on when asked – just like Oracle told us it would. Pretty straightforward.

Source: https://www.optiv.com/blog/exploiting-jmx-rmi

I was reading the above article, and I noticed that it appears as if Seldon-Core has this vulnerability. Does anyone know if this is a concern. What is the rationale behind these option values?

@ukclivecox ukclivecox added this to the 1.1 milestone Mar 25, 2020
@ukclivecox ukclivecox self-assigned this Mar 25, 2020
@ukclivecox
Copy link
Contributor

As discussed in Slack you can update the JAVA_OPS via an environment variable. https://docs.seldon.io/projects/seldon-core/en/v1.0.2/graph/annotations.html#service-orchestrator

However, we should remove this as the default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants