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

command injection vulnerability #9047

Closed
mr4ndr3w opened this issue May 8, 2024 · 4 comments
Closed

command injection vulnerability #9047

mr4ndr3w opened this issue May 8, 2024 · 4 comments
Labels

Comments

@mr4ndr3w
Copy link

mr4ndr3w commented May 8, 2024

Heya,

I found 2 high critical security issues:
command injection vulnerabilities

plugin/cache
/plugin/CloneSite

Where I can report them? And who will request cve?

@mr4ndr3w mr4ndr3w added the bug label May 8, 2024
@DanielnetoDotCom
Copy link
Member

Hi, can you please send it to my email developer@youphptube.com

also if you have a CVE link, please send it to, me so I can give you the credits for the fix

@mr4ndr3w mr4ndr3w closed this as not planned Won't fix, can't repro, duplicate, stale May 8, 2024
@mr4ndr3w mr4ndr3w reopened this May 8, 2024
@mr4ndr3w
Copy link
Author

mr4ndr3w commented May 8, 2024

check email

@mr4ndr3w
Copy link
Author

mr4ndr3w commented May 8, 2024

can you request a CVE identification number from GitHub?

@DanielnetoDotCom
Copy link
Member

DanielnetoDotCom commented May 8, 2024

Thank you for your email and for highlighting the vulnerabilities. Upon review, it appears that these vulnerabilities can only be exploited if an attacker has already obtained administrative access to the server. Here's a brief overview:

  1. Vulnerability 1 (/plugin/CloneSite): Requires admin access to the server or SSH root access to the site to be cloned.
  2. Vulnerability 2 (Cache): Also necessitates admin access to the server.

Given that these scenarios involve an attacker who already has high-level access, further exploitation would be redundant, as the server is compromised in more significant ways at that point. Unless I'm mistaken, I believe no immediate action or fix is necessary for these particular vulnerabilities under the described conditions.

@mr4ndr3w mr4ndr3w closed this as completed May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants