By Deeba Ahmed
The KmsdBot was known for targeting both Linux and Windows devices.
This is a post from HackRead.com Read the original post: A Syntax Error Led to Crashing of KmsdBot Cryptomining Botnet

KmsdBot was a newly discovered cryptocurrency mining botnet killed accidentally by Akamai’s team of researchers while researching on KmsdBot. According to researchers, a syntax error caused it to stop sending commands, which destroyed the botnet.

**What is KmsdBot?**

Named by Akamai Security Intelligence Response Team (SIRT) in November 2022, KmsdBot is was a **crypto mining botnet** equipped with command-and-control abilities. It infected victims by exploiting weak credentials and SSH via brute force.

The Akamai team assessed and **reported** on the botnet after one of its honeypots got infected. The botnet targeted both **Linux and Windows devices** using a range of microarchitectures to deploy mining software and include the compromised hosts in its DDoS bot army. Its main targets included gaming and tech firms and luxury vehicle makers.

1.  **Dangerous WireX Android DDoS Botnet Killed by Security Giants**
2.  **Andromeda Botnet that infected millions of devices is dismantled**
3.  **Mirai botnet resurfaces with MooBot variant against D-Link devices**
4.  **Russian Rsocks Botnet Powered by Millions of IoT Devices dismantled**
5.  **FBI Disrupts Cyclops Blink Botnet Used by Russian Intelligence agency**

**Incident Details**

In a **blog post**, Larry W. Cashdollar, a researcher at Akamai, the commands sent to the botnet while assessing its operational mechanism within a controlled environment mistakenly led to the malware’s neutralization.

After a single “improperly formatted command,” Cashdollar explains, the bot stopped sending any command. This could be possible because of the absence of an internal error-checking feature built into its source code to verify the incoming commands. 

So, any instruction given without a space between the port and the target website caused the Go binary on the infected device to crash entirely and stop communicating with its C2 server. Hence, this **killed the botnet**.

Since the botnet doesn’t feature a persistence mechanism, the malware operators will need to re-infect the devices once again and rebuild the entire infrastructure from scratch.

“This botnet has been going after some very large luxury brands and gaming companies, and yet, with one failed command it cannot continue. This is a strong example of the fickle nature of technology and how even the exploiter can be exploited by it,” Cashdollar explained.

A Syntax Error Led to Crashing of KmsdBot Cryptomining Botnet

New web targets for the discerning hacker

New web targets for the discerning hacker

Bug bounty platform HackerOne has launched a scheme to encourage customers to adopt a standard policy geared towards protecting hackers from potential legal problems.

The Gold Standard Safe Harbor (GSSH) is designed to be “short, broad, \[and\] easily-understood”, according to HackerOne.

Many bug bounty and vulnerability disclosure programs offer safe harbor agreements that allow hackers acting in good faith to do their thing. HackerOne’s standard policy is designed to collate best practices while reducing the administrative burden for hackers, who will have no need to scrutinize the terms and conditions of targets before looking for in-scope vulnerabilities.

European crowdsourced security platform Intigriti, meanwhile, has launched Bug Bounty Calculator, a tool designed to help bug bounty program owners pitch their payout rates at the appropriate level.

To generate reward suggestions program providers select their industry and describe their assets in terms of risk level, maturity level, and incentive curve.

Inti de Ceukelaire, head of hackers at Intigriti, explained why he built the tool: “Anyone can set up a bug bounty program, but if you aren’t sure what you’re doing, you may pay too much for vulnerabilities. Even worse, set your bounties too low and you may not attract any researchers at all.”

The maximum payout awards under a growing number of programs have reached $1 million and more. Earlier this week The Daily Swig took a closer look into these high potential reward programs and discovered that market forces, in particular a scarcity of skilled talent, are driving up the value of rewards offered.

Web 3.0 and crypto platforms, in particular, are competing to offer dazzlingly high potential rewards. However, experts questioned by The Daily Swig pointed out the rarity of firms in this arena actually paying out seven-figure sums, which suggests some are offering enormous potential bounties in an attempt to court publicity.

Against this are several examples of six-figure payouts by more established tech vendors such as Apple and Intel. However, HackerOne reports that the median payouts for critical vulnerabilities comes in at $3,000 – a figure worth bearing in mind by anyone tempted to quit their day job in pursuit of greater riches on the bug bounty circuit.

An example of an interesting flaw on the lower end of the scale dropped early in November when a researcher revealed that they had earned a $250 bug bounty payout after discovering a code injection flaw in Acronis’ cloud management console that could be abused for data theft.

On November 4, ‘Medi’ (under the alias ‘mr-medi’), published a technical analysis of the client-side path traversal flaw, which they described as the “favorite bug” they’d ever found.

**The latest bug bounty programs for December 2022**

The past month saw the arrival of several new bug bounty programs. Here’s a list of the latest entries:

**Abraxas (enhanced)**

**Program provider:  
**Bug Bounty Switzerland

**Program type:  
**Public

**Max reward:  
**CHF 30,000 ($26,167)

**Outline:  
**Abraxas, which provides IT services for the government and public sector in Switzerland, has tripled maximum payouts from 10,000 Swiss francs to 30,000 francs.

**Notes:  
**Program has a particular focus on vulnerabilities that could enable attackers to manipulate the outcome of Swiss elections.

Check out the Abraxas bug bounty page for more details

**Amber AI**

**Program provider:  
**HackerOne

**Program type:  
**Public

**Max reward:  
**$5,000

**Outline:  
**AMBER AI, a “crypto-finance service provider”, is offering between $2,500 and $5,000 for the submission of valid critical bugs.

**Notes:  
**Vulnerabilities in AMBER AI’s core business services qualify for the highest payout tier but the web 3.0 business is also interested in a wide range of web security vulnerabilities such as SQL injection, CSRF, and denial-of-service issues.

Check out the AMBER AI bug bounty page for more details

**Expedia Group**

**Program provider:  
**HackerOne

**Program type:  
**Public

**Max reward:  
**$5,000

**Outline:  
**Expedia runs a portfolio of travel websites that offer hotel, flight booking, and more.

**Notes:  
**A range of targets are in scope including hotels.com. orbitz.com, and expedia.com.

Check out the Expedia Group bug bounty page for more details

**Magic Eden**

**Program provider:  
**HackerOne

**Program type:  
**Public

**Max reward:  
**$2,500

**Outline:  
**Magic Eden styles itself as a community-centric NFT marketplace.

**Notes:  
**The bug bounty program is focused on smart contracts and on guarding against the freezing of funds, direct theft, denial of business function, or other attacks that interfere with the smooth operation of the marketplace.

Check out the Magic Eden bug bounty page for more details

**Teleport**

**Program provider:  
**HackerOne

**Program type:  
**Public

**Max reward:  
**$5,000

**Outline:**

Teleport offers open source technology based around the zero trust model and designed for the administration of servers and cloud-based applications.

**Notes:  
**Vulnerabilities in both the on-premises software and cloud-based versions of Teleport’s technologies fall within the scope of the program.

Check out the Teleport bug bounty page for more details

**ThousandEyes**

**Program provider:  
**Bugcrowd

**Program type:  
**Public

**Max reward:  
**$4,500

**Outline:  
**ThousandEyes, which offers network intelligence software, has invited elite hackers to probe five targets for security flaws.

**Notes:  
**In-scope targets include ThousandEyes' website, application platform, customer-accessible API, and enterprise and agent software. The firm reopened its previously dormant bug bounty program in late November.

Check out the ThousandEyes bug bounty page for more details

**ZeroBounce**

**Program provider:  
**HackerOne

**Program type:  
**Public

**Max reward:  
**$3,000

**Outline:  
**ZeroBounce offers email marketing services, targeted towards the needs of enterprise customers.

**Notes:  
**A broad array of web security vulnerability (such as XSS) on the zerobounce.in domain and flaws in the associated API library (api.zerobounce.in) are within scope.

Check out the ThousandEyes bug bounty page for more details

PREVIOUS EDITION Bug Bounty Radar // The latest bug bounty programs for November 2022

Bug Bounty Radar // The latest bug bounty programs for December 2022

An ongoing analysis into an up-and-coming cryptocurrency mining botnet known as KmsdBot has led to it being accidentally taken down.
KmsdBot, as christened by the Akamai Security Intelligence Response Team (SIRT), came to light mid-November 2022 for its ability to brute-force systems with weak SSH credentials.
The botnet strikes both Windows and Linux devices spanning a wide range of

An ongoing analysis into an up-and-coming cryptocurrency mining botnet known as **KmsdBot** has led to it being accidentally taken down.

KmsdBot, as christened by the Akamai Security Intelligence Response Team (SIRT), came to light mid-November 2022 for its ability to brute-force systems with weak SSH credentials.

The botnet strikes both Windows and Linux devices spanning a wide range of microarchitectures with the primary goal of deploying mining software and corralling the compromised hosts into a DDoS bot.

Some of the major targets included gaming firms, technology companies, and luxury car manufacturers.

Akamai researcher Larry W. Cashdollar, in a new update, explained how commands sent to the bot to understand its functionality in a controlled environment inadvertently neutralized the malware.

"Interestingly, after one single improperly formatted command, the bot stopped sending commands," Cashdollar said. "It's not every day you come across a botnet that the threat actors themselves crash their own handiwork."

This, in turn, was made possible due to the lack of an error-checking mechanism built into the source code to validate the received commands.

Specifically, an instruction issued without a space between the target website and the port caused the entire Go binary running on the infected machine to crash and stop interacting with its command-and-control server, effectively killing the botnet.

The fact that KmsdBot doesn't have a persistence mechanism also means that the malware operator will have to re-infect the machines again and re-build the infrastructure from scratch.

"This botnet has been going after some very large luxury brands and gaming companies, and yet, with one failed command it cannot continue," Cashdollar concluded. "This is a strong example of the fickle nature of technology and how even the exploiter can be exploited by it."

Found this article interesting? Follow us on Twitter __ and LinkedIn to read more exclusive content we post.

Researchers 'Accidentally’ Crash KmsdBot Cryptocurrency Mining Botnet Network

Multiple Xiongmai NVR devices, including MBD6304T V4.02.R11.00000117.10001.131900.00000 and NBD6808T-PL V4.02.R11.C7431119.12001.130000.00000, allow authenticated users to execute arbitrary commands as root, as exploited in the wild starting in approximately 2019. A remote and authenticated attacker, possibly using the default admin:tlJwpbo6 credentials, can connect to port 34567 and execute arbitrary operating system commands via a crafted JSON file during an upgrade request. Since at least 2021, Xiongmai has applied patches to prevent attackers from using this mechanism to execute telnetd.

CVE-2022-45045: Xiongmai IoT Exploitation - Blog - VulnCheck

Digital Alert Systems’ DASDEC software prior to version 4.1 contains a cross-site scripting (XSS) vulnerability that allows remote attackers to inject arbitrary web script or HTML via the SSH username, username field of the login page, or via the HTTP host header. The injected content is stored in logs and rendered when viewed in the web application.

Overview 

A cross-scripting (XSS vulnerability via the Host Header was identified in certain pages after login, where remote attackers could inject arbitrary web script or HTML code.  

Vulnerability Details 

CVSS V3 Base Score – AV:N/AC:L/PR:L/UI:R/S:C/C:N/I:L/A:N 

CWE-79 

Digital Alert Systems is issuing a follow-on advisory to its 2019 advisory relating to cross-scripting (XSS) vulnerabilities. An   
additional vulnerability was identified in certain pages after login, which presents the potential risk for remote attackers to inject arbitrary web scripts of HTML code. Exploitable remote/low attack complexity/public exploits are available. 

Affected Products and Versions 

Product: DASDEC / One-Net  
Versions: all software versions (CVE-2022-40204) 

Remediation 

*   DAS issued a patch for the 2019 XSS security issue (CVE-2019-18265) in version 4.1, released in October 2019.  The latest version can be downloaded from the following location: https://www.digitalalertsystems.com/software-updates  
    
*   A patch for the 2022 XSS security issue (CVE-2022-40204) will be available shortly.  Information about the availability of this software update will be sent directly to registered DASDEC users and will be posted on our website. 
    
*   All DASDEC users are strongly encouraged to register or update their customer information. 
    

General security best practices 

*   Regularly update/patch DASDEC EAS device software to the latest version available. 
    
*   Restrict exposure to external networks for all DASDEC EAS devices and ensure they are not directly accessible from the open Internet. 
    
*   Deploy DASDEC EAS devices behind barrier devices (e.g. firewalls) and isolate them from business networks. 
    
*   Remote access to DASDEC EAS devices should be made available on a strict need-to-use basis. Remote access should use secure methods, such as Virtual Private Networks (VPNs). 
    
*   Review DASDEC security logs for suspect activity. 
    
*   Disable/deactivate unused communication channels, TCP/UDP ports and services on networked devices. 
    
*   Perform regular security assessments and risk analysis of critical systems, such as EAS devices. 
    

​

Acknowledgment 

*   CVE-2022-40204 – Ken Pyle 
    

**November 2022 DAS Vulnerability Advisory**

Cross-scripting (XSS) vulnerability 

**Date**

**Overall Risk**

**CVSS 3.0**

11/22/2022

Moderate

4.1

**August 2022 Update**

In 2019, we became aware of vulnerabilities relating to DASDEC/One-Net software relating to cross-site scripting and other potential issues. We launched an investigation to identify potentially affected products and assess risk. In 2019, Digital Alert Systems released the version 4 series of software, which addressed these vulnerabilities along with a host of new features.  
 

Older software versions that may be vulnerable are:  
     •    v2.x series software (Status: deprecated. End-of-life 12/21/2016)\*  
     •    v3.x series software (Status: deprecated. End-of-life 7/1/2019)  
 

Software versions 4.1 (release date Oct. 2019) and above include mitigations for the identified issues.  
 

We strongly recommend updating your DASDEC/One-Net software if it is earlier than V4.1 to ensure it contains the latest operational revisions, security patches, and regulatory compliance updates.  
 

As we have repeatedly urged, sensitive equipment like the DASDEC/One-Net must be operated within a firewall and other protective measures. EAS equipment of any type should never be placed with direct access to the Internet.  
 

We thank the researcher for identifying these issues at the time and following responsible disclosure practices.

  
\* For product end-of-support and end-of-life status.

Digital Alert Systems continually strives to improve its products and services for our customers, but we can’t do it all alone - we need your help. In the world of Internet-connected devices, a strong vigilant focus on security is promoted by properly installing and maintaining your EAS equipment. Keeping your EAS gear behind strong firewalls and in a secure network helps create a critical barrier to unauthorized entry or exploitation. Further, maintaining your EAS device with current software updates is a key part of keeping up to date with critical security patches.  
 

These devices are not security appliances themselves and are designed to operate BEHIND A PROPER FIREWALL!  
 

By properly maintaining the equipment you form the crucial link in this security chain.   
 

If you have questions, concerns or reports regarding the security of your product, contact the Digital Alert Systems security team at security@digitalalertsystems.com, or telephone (585) 765-2254

**Resources**

Over the years we have released several resources on security postures to help our customers and the industry overall understand why security is so important and how it can be done. Here are just two examples:

**Understanding Security for Your EAS Equipment**

**CAP, EAS and IPAWS:  Introducing a Defense-in-Depth Security Strategy for Broadcasters**

**Customer Contacts**

In order to quickly communicate with our customers, it is important we are provided with current contact information on your product registration, and kept informed of any changes. This way we can communicate details on security information, vulnerabilities, and software security patches quickly and directly. We rely on you to ensure we have the most current contact information for your organization. If you haven’t completed the registration process or need to update the information please follow this link to the product registration page to provide your contact details.  
 

It is the customer’s responsibility to properly configure, secure and maintain this equipment.† From time to time security scans are done to identify devices improperly connected to the open Internet. If you are contacted by a member of our security team, please understand our representative will be looking to advise you of the issue and help in properly securing the equipment. 

**The representative will be looking to assist you in one or more of the following areas:**

Removing your EAS device from the public Internet

Turning off unnecessary services

Changing the default credentials

When appropriate, assisting in firmware upgrades to the EAS device.

**The representative will NOT:**

Ask for log in credentials

Access the device without written permission

† See, for example, FCC-CIRC1807-04.

**Report a Product Security Issue or Vulnerability**

Digital Alert Systems’ security assistance team is responsible for vulnerability management and overseeing and refining product security practices. The team will give reports and questions the attention they demand, including prompt acknowledgement, detailed responses, and, ultimately, the investigation and fixing of legitimate vulnerabilities.  
 

We respectfully ask anyone who discovers a product security vulnerability follow our Vulnerability Reporting Policy thus ensuring proper discovery and handling of any issues.   
 

Should there be any product security-related issues or questions please privately contact our security assistance team via email at security@digitalalertsystems.com

**When reporting an issue, please include as many details as possible, such as:**

Version numbers

Steps to reproduce the issue 

Screenshots 

Any other details that will help us validate the issue

We ask that you do not share any vulnerability details until we have responded, and that you allow a reasonable time frame for a response.

We hope this information combined with our service and support will help you and the industry keep a diligent watch over the critical EAS infrastructure.  
 

Should you have any question please don't hesitate to contact us at security@digitalalertsystems.com or support@digitalalertsystems.com. Also, by telephone at +1 (585) 765-1155  
 

Thank you,  
The Digital Alert Systems Security Team

CVE-2019-18265: Security Advisory | DAS 2022

Book Store Management System v1.0 was discovered to contain hardcoded credentials which allows attackers to escalate privileges and access the admin panel.

Book Store Management System— Use of Hard-coded Credentials in Source Code Leads to Admin Panel Access

Exploit Author: Upasana Bohra

Vendor Homepage: https://www.sourcecodester.com/php-project

Software Link: https://www.sourcecodester.com/php/15748/book-store-management-system-project-using-php-codeigniter-3-free-source-code.html

Tested on Windows10

Linkedln Contact: https://www.linkedin.com/in/upasana-bohra-8767b9156/

Hardcoded Credentials:

Hardcoded Passwords, also often referred to as Embedded Credentials, are plain text passwords or other secrets in source code. Password hardcoding refers to the practice of embedding plain text (non-encrypted) passwords and other secrets (SSH Keys, DevOps secrets, etc.) into the source code. Default, hardcoded passwords may be used across many of the same devices, applications, systems, which helps simplify set up at scale, but at the same time, poses a considerable cybersecurity risk.

\[Attack Vectors\]

An attacker can gain admin panel access using default credentials and do malicious activities

PROOF OF CONCEPT

1 Download source code from https://www.sourcecodester.com/php/15748/book-store-management-system-project-using-php-codeigniter-3-free-source-code.html

2 Now unzip it and go to the Database folder here we can see one SQL file.

3 Now open that file using Notepad and there we can see admin credentials. but the password is encrypted .from pattern I identified that this is MD5 hash. so we can easily decrypt using crackstation.net or any hash cracker tools like Hashcat, John the ripper.

CVE-2022-44097: Book Store Management System— Use of Hard-coded Credentials in Source Code Leads to Admin Panel Access · Issue #2 · upasvi/CVE-

Sanitization Management System v1.0 was discovered to contain hardcoded credentials which allows attackers to escalate privileges and access the admin panel.

Sanitization Management System — Use of Hard-coded Credentials in Source Code Leads to Admin Panel Access

Exploit Author: Upasana Bohra

Vendor Homepage: https://www.sourcecodester.com/php-project

Software Link: https://www.sourcecodester.com/php/15770/sanitization-management-system-project-php-and-mysql-free-source-code.html

Tested on Windows10

Linkedln Contact: https://www.linkedin.com/in/upasana-bohra-8767b9156/

Hardcoded Credentials:

Hardcoded Passwords, also often referred to as Embedded Credentials, are plain text passwords or other secrets in source code. Password hardcoding refers to the practice of embedding plain text (non-encrypted) passwords and other secrets (SSH Keys, DevOps secrets, etc.) into the source code. Default, hardcoded passwords may be used across many of the same devices, applications, systems, which helps simplify set up at scale, but at the same time, poses a considerable cybersecurity risk.

\[Attack Vectors\]

An attacker can gain admin panel access using default credentials and do malicious activities

Proof Of Concept

1 Download source code from https://www.sourcecodester.com/php/15770/sanitization-management-system-project-php-and-mysql-free-source-code.html

2 Now unzip it and go to the Database folder here we can see one SQL file.

3 Now open that file using Notepad and there we can see admin credentials. but the password is encrypted .from pattern I identified that this is MD5 hash. so we can easily decrypt using crackstation.net or any hash cracker tools like Hashcat, John the ripper.

CVE-2022-44096: Sanitization Management System  — Use of Hard-coded Credentials in Source Code Leads to Admin Panel Access · Issue #1 · upasvi/CVE-

The vulnerability, disclosed In October, gives an unauthenticated attacker a way to take control of an affected product.

Fortinet customers that have not yet patched a critical authentication bypass vulnerability that the vendor disclosed in October in multiple versions of its FortiOS, FortiProxy, and FortiSwitch Manager technologies now have an additional reason to do so quickly.

At least one threat actor, operating on a Russian Dark Web forum, has begun selling access to multiple networks compromised via the vulnerability (CVE-2022-40684), and more could follow suit soon. Researchers from Cyble who spotted the threat activity described the victim organizations as likely using unpatched and outdated versions of FortiOS.

**Selling Access to Compromised Networks**

Dhanalakshmi PK, senior director of malware and research intelligence at Cyble, says the company's available intelligence indicates the threat actor might have access to five major organizations via the vulnerability. Cyble's analysis showed the attacker attempting to add their own public key to the admin user's account on the compromised systems.

"An attacker can update or add a valid public SSH key to a targeted account on a system and can then typically gain complete access to that system," Dhanalakshmi says. "Additionally, the threat actor could launch other attacks against the rest of the IT environment with the foothold and knowledge gained through exploiting this vulnerability."

Cyble said a scan it conducted showed more than 100,000 Internet-exposed FortiGate firewalls, a substantial number of which are likely exploitable because they remain unpatched against the vulnerability

Fortinet publicly disclosed CVE-2022-40684 on Oct. 10, a few days after privately notifying customers of affected products about the threat. The vulnerability essentially gives an unauthenticated attacker a way to gain full control of an affected Fortinet product by sending it specially crafted HTTP and HTTPS requests. Security researchers have described the vulnerability as easy to find and trivial to exploit because all that an attacker needs to do is gain access to the management interface of a vulnerable system.

**Popular Target for Attackers**

When Fortinet disclosed the vulnerability, it urged customers to immediately update to patched versions of the affected products and warned of active exploit activity targeting the flaw. It also urged companies that could not update to immediately disable HTTPS administration on their vulnerable Internet-facing Fortinet products. The US Cybersecurity and Infrastructure Security Agency (CISA) promptly listed the flaw its catalog of known exploited vulnerabilities and gave federal civilian agencies until Nov. 1, 2022, to address the issue.

Much of the concern stemmed from the popularity of Fortinet products — and technologies from other vendors in the same network edge category — among threat actors. Soon after Fortinet disclosed the flaw, proof-of-concept code for exploiting it became publicly available, and security vendors reported large-scale scanning activity targeting the flaw. The number of unique IP addresses targeting the flaw soared in a matter of days from the single digits to more than 40.

And that number has grown. James Horseman, exploit developer at Horizon3ai, a security vendor that did much of the initial research around the vulnerability, says the number of unique IPs currently targeting the Fortinet flaw has risen to 112, according to data from GreyNoise, which tracks malicious scanning activity on the Internet.

"These Fortinet devices are typically Internet-facing for corporations and are seldom monitored," adds Zach Hanley, chief attack engineer at Horizon3ai. "This combination makes it great for sustained initial access into a network for threat actors who are looking to conduct reconnaissance, deploy ransomware, steal data, etc."

Threat actors have hammered away in similar fashion at other Fortinet flaws for the same reason. Notable examples include CVE-2018-13379, CVE-2020-12812, and CVE-2019-5591, a set of three flaws that Iran-backed threat groups were observed exploiting in numerous attacks. In April 2021, the FBI and CISA warned of other advanced persistent threat groups exploiting the same set of flaws in attacks against organizations in the US and elsewhere.

.

Cyberattackers Selling Access to Networks Compromised via Recent Fortinet Flaw

Data Integrity Failure in 'Backup Config' in D-Link DNR-322L <= 2.60B15 allows an authenticated attacker to execute OS level commands on the device.

Skip to content

GitLab

*   *   GitLab: the DevOps platform
    *   Explore GitLab
    *   Install GitLab
    *   How GitLab compares
    *   Get started
    *   GitLab docs
    *   GitLab Learn
    
*   Pricing
*   Talk to an expert

*   /
    
*   

*   Help
    
    *   Help
    *   Support
    *   Community forum
    
    *   Submit feedback
    *   Contribute to GitLab
    *   Switch to GitLab Next
    
*   *   
    
    Projects Groups Snippets
    
*   Sign up now
*   Login
*   Sign in / Register
    

*   luka
*   CVE-2022-40799

C

**CVE-2022-40799**

Project ID: 39762712

Star 0

*   **2** Commits
*   **1** Branch
*   **0** Tags
*   **195 KB** Project Storage
    

Topics: CVE

D-Link DNR-322L - Authenticated Remote Code Execution

Switch branch/tag

Find file

**Download source code**

zip tar.gz tar.bz2 tar

Clone

*   Clone with SSH
*   Clone with HTTPS

*   Open in your IDE
    
    Visual Studio Code (SSH)
    
    Visual Studio Code (HTTPS)
    
    IntelliJ IDEA (SSH)
    
    IntelliJ IDEA (HTTPS)
    

*   **Copy SSH clone URL**git@gitlab.com:lu-ka/cve-2022-40799.git
*   **Copy HTTPS clone URL**https://gitlab.com/lu-ka/cve-2022-40799.git

*   README
*   MIT License

Tag

#ssh