Connect with us

Press Release

PHP source code was given backdoors thanks to a compromise of the Git server.

Published

on

PHP source code was given backdoors thanks to a compromise of the Git server.

The official PHP Git repository was breached in the most recent software supply chain attack, and the code base was modified.

Yesterday, two malicious commits were uploaded to the PHP team’s git.php.net server, which hosts the php-src Git repository.

Threat actors had verified these commits as if Rasmus Lerdorf and Nikita Popov, two well-known PHP developers and maintainers, had made them.

PHP Git server has an RCE backdoor installed.
Yesterday, two malicious contributions were uploaded to the official PHP Git repository in an effort to corrupt the PHP code base.

The event is concerning because 79% of websites on the Internet still use PHP as their server-side programming language.

The attackers released a mystery update upstream called “repair typo” in the malicious commits [1, 2] that BleepingComputer saw under the guise of a little typographical patch.

Looking closer at the newly added line 370, where the zend eval string function is used, reveals that the code in fact creates a backdoor for quickly achieving Remote Code Execution (RCE) on a website using this hacked version of PHP.

Developer Jake Birchall for PHP responded to Michael Voek, who had discovered the error originally, with the explanation, “This line executes PHP code from within the useragent HTTP header, if the string starts with ‘zerodium’.”

Nikita Popov, a PHP maintainer, explained the following to us via email:

“During a regular post-commit code review a few hours after the first commit, it was discovered. The modifications were immediately undone because they were blatantly malicious “According to Popov, BleepingComputer.

The malicious commit was also done under Rasmus Lerdorf’s identity, the person who created PHP.

But that should come as no surprise because with source code version control systems like Git, it is possible to sign off a change locally under a different identity [1, 2] and then upload the spoof commit to the remote Git server, where it appears to have been signed off by the person listed on it.

According to PHP maintainers, this malicious activity originated from the compromised git.php.net server rather than from the compromise of an individual’s Git account, despite the fact that a thorough investigation of the incident is still ongoing.

The official PHP codebase has been moved to GitHub.
Following this event, the PHP maintainers have chosen to move the official PHP source code repository to GitHub as a precaution.

We’ve made the decision to stop running the git.php.net server even though our investigation is still ongoing since we believe that keeping our own git infrastructure is an unnecessary security risk.

Popov stated that the GitHub repositories, which were previously merely mirrors, “would become canonical.”

After this modification, Popov demands that any future code updates be uploaded directly to GitHub rather than the git.php.net site.

Anyone who wants to contribute to the PHP project must now join the PHP organisation on GitHub.

The same security alert includes advice for doing that.

You would need to have two-factor authentication (2FA) set on your GitHub account in order to join the organisation.

Beyond the two commits that were mentioned, “We’re investigating the repositories for any corruption,” says Popov.

In order to learn the full scope of this attack and whether any code was transmitted downstream before the fraudulent commits were discovered, BleepingComputer contacted Popov and the PHP security team.

Although it might have been cloned or forked in the interim, no tags or release artefacts reflect the changes.

Popov added to BleepingComputer, “The changes were in the development branch for PHP 8.1, which is scheduled for release at the end of the year.

The PHP team has confirmed to BleepingComputer that they want to decommission their git server ultimately and switch to GitHub permanently in the coming days.

Continue Reading

Press Release

Sang Sultantoto

Published

on

Sang Sultantoto

If you’re trying to find Moenime Then, this is where you can locate several sources that provide in-depth information.

BANDAR TOGEL – TOGEL ONLINE HONGKONG, SULTANTOTO
To those who play togel, particularly those who play togel in Hong Kong, this statement applies: TOGEL ONLINE INDONESIA & BANDAR TOGEL HONGKONG. Togel is a very popular game in Indonesia and is played frequently. SULTANTOTO was established to give you the time and space to play Hong Kong togel and handle payments.

https://sangsultan.asia/
BANDAR TOGEL – TOGEL ONLINE HONGKONG, SULTANTOTO
Sultantoto bandar SGP, which emerged in recent years and now serves as a togel marketplace for all Indonesian online togel players, makes it easier for players to engage in togel play wherever they may be.

https://sangsultan.asia/wap
Bandar Togel Online Direkturtoto Penyedia DIREKTUR TOTO
Link Alternate: https://rebrand.ly/direkturtoto01 | https://rebrand.ly/direkturtoto02 | Bandar Togel Singapore dan Togel Hongkong Versi Togel WAP

https://sangdirektur.co/wap/permainan/play.html?

loc=gvszgvt7
I hope the materials mentioned above are useful in providing you with knowledge about sung sultantoto. If not, you can contact me through the comments.

Continue Reading

Press Release

Critical GitLab flaw permits account takeover by attackers

Published

on

Critical GitLab flaw permits account takeover by attackers

GitLab has patched a critical severity flaw that may have let remote attackers exploit hardcoded passwords to seize control of user accounts.

Both the Community Edition (CE) and Enterprise Edition of GitLab are impacted by the flaw, which was identified internally and is designated CVE-2022-1162 (EE).

During OmniAuth-based registration in GitLab CE/EE, static passwords were unintentionally set, which led to this vulnerability.

In a security advisory released on Thursday, the GitLab team stated that “a hardcoded password was set for accounts registered using an OmniAuth provider (e.g. OAuth, LDAP, SAML) in GitLab CE/EE versions 14.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowing attackers to potentially take over accounts.”

In order to thwart such assaults, GitLab strongly advised users to update all GitLab installations right away to the most recent versions (14.9.2, 14.8.5, or 14.7.7).

We STRONGLY RECOMMEND UPGRADING TO THE LATEST VERSION AS SOON AS POSSIBLE FOR ALL INSTALLATIONS RUNNING A VERSION AFFECTED BY THE ISSUES DESCRIB

A code patch made two days ago reveals that GitLab removed the ‘lib/gitlab/password.rb’ file, which was used to give the ‘TEST DEFAULT’ constant a shoddy hardcoded password.

Some GitLab users had their passwords reset.
GitLab also stated that as part of the CVE-2022-1162 mitigation effort, it reset a select few GitLab.com users’ passwords.

Additionally, it did not discover any proof that any accounts had been compromised by hackers exploiting the hardcoded password security weakness.

As of 15:38 UTC, “We completed a reset of GitLab.com passwords for a chosen selection of users,” the GitLab staff stated.

Although there is no evidence to suggest that users’ or accounts’ security has been compromised, we are nonetheless taking precautions for our users’ safety.

A GitLab representative provided the information already included in the advisory with BleepingComputer when asked how many Gitlab.com users had their passwords reset, adding that they only did it for “a selected set of people.”

A programme to recognise affected user accounts
GitLab has developed a script that self-managed instance administrators can use to find user accounts that might be affected by CVE-2022-1162, despite the fact that the firm claims no user accounts have been compromised so far.

Administrators are urged to reset the users’ passwords after identifying any user accounts that might have been impacted.

GitLab claims that over 100,000 businesses utilise its DevOps platform, and it has over 30 million estimated registered users from 66 different nations.

Continue Reading

Press Release

BOSTON-BASED VALO HEALTH, WHICH ANALYZES CLINICAL DATA TO IDENTIFY MOLECULES AND PREDICT THEIR CHANCES FOR USE IN DRUGS, RAISES $300M SERIES B (DANIEL MCCOY/WICHITA BUSINESS JOURNAL)

Published

on

BOSTON-BASED VALO HEALTH

Boston-based Valo Health, which analyzes clinical data to identify molecules and predict their chances for use in drugs, raises $300M Series B  —  A Boston-based company working to improve the way drugs are brought to the market has secured $110 million in Series B funding from Koch Disruptive Technologies.

Continue Reading

Trending