CVE-2023-38829: GitHub - adhikara13/CVE-2023-38829-NETIS-WF2409E

Skip to content

• • Actions

    Automate any workflow

  • Packages

    Host and manage packages

  • Security

    Find and fix vulnerabilities

  • Codespaces

    Instant dev environments

  • Copilot

    Write better code with AI

  • Code review

    Manage code changes

  • Issues

    Plan and track work

  • Discussions

    Collaborate outside of code

• • GitHub Sponsors

    Fund open source developers

*   The ReadME Project
    
    GitHub community articles

• Pricing

Search code, repositories, users, issues, pull requests…

Provide feedback

Saved searches****Use saved searches to filter your results more quickly

Sign up

• Notifications

• Fork 0

• Code

• Issues

• Pull requests

• Actions

• Projects

• Security

• Insights

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

1 branch 0 tags

Code

• Use Git or checkout with SVN using the web URL.

• Open with GitHub Desktop

• Download ZIP

Latest commit

FilesPermalink

Failed to load latest commit information.

Type

Name

Latest commit message

Commit time

CVE-2023-38829-NETIS-WF2409E****NETIS SYSTEMS Router WF2409E Command Injection PoC****Vulnerability Description:

The ping and traceroute functions of the NETIS SYSTEMS Router WF2409E (version V3.6.42541) are susceptible to command injection attacks. Malicious input can be crafted in the parameters of these functions through the Web admin management interface, allowing arbitrary commands to be executed with the privileges of the affected process.

PoC Steps:

1. Identify the Target:

   • Ensure you have access to the NETIS SYSTEMS Router WF2409E (version V3.6.42541) Web admin management interface.

2. Open the Ping Function:

   • Log in to the router’s web interface.
   • Navigate to the “Diagnostic Tools” section.
   • Select the “Ping” function.

3. Craft Malicious Input:

   • In the “Ping” function input field, inject a command. For example:

4. Execute the Command:

   • Submit the crafted input.
   • Observe the output. If the directory listing of the router’s filesystem is displayed, the command injection is successful.

5. Open the Traceroute Function:

   • Navigate back to the “Diagnostic Tools” section.
   • Select the “Traceroute” function.

6. Craft Malicious Input:

   • In the “Traceroute” function input field, inject a command. For example:

7. Execute the Command:

   • Submit the crafted input.
   • Check if the output includes the result of the ls command. If so, the command injection is demonstrated.

Notes:

• This PoC is for educational and responsible disclosure purposes only.
• Do not use this PoC on systems you don’t have permission to test.
• Ensure you have proper authorization before attempting any security testing.