Ir al contenido principal

What You Need to Know About MongoDB Attacks

Attacks and other hacks on IT systems are, unfortunately, on the rise; the most recent one to make headlines is the attack on MongoDB.

The knowledge that a MongoDB attack removes all of the victim’s data and replaces it with a ransom note is upsetting, and the fact that tens of thousands of MongoDB databases holding more than 680 terabytes of data have been compromised and held hostage is downright alarming.
The MongoDB attacks, which have been a problem for approximately a month, are still occurring, and the number of attacks is on the rise; sources say that 25% of unsecured internet-accessible MongoDB databases have been hit by this ransomware attack.

What is MongoDB?

MongoDB is a free, open-source database system that runs on a range of platforms, including Windows. Its usage is growing quickly, with millions of downloads – something that will only prove to increase the number of attacks.

Now, as this article explains, five groups of attackers are competing to delete as many publicly accessible MongoDB databases as possible.

Although this is not a hack in the traditional sense, as it appears to affect only open databases connected to the public internet without a password protecting the administrator account, doesn’t mean you shouldn’t be actively protecting yourself against the possibility of an attack.

How to Protect YourselfMongoDB attack

Some Sage Enterprise Management components include MongoDB, and recent communications from Sage indicate the need to take action to protect all ports on your servers as a matter of security best practices, whether or not the ports are connected to the public internet.

It is critical to take the following steps to ensure protection from this attack or other, similar attacks.

We recommend:
  • Password protecting your system and administrator accounts
  • Preventing server ports from being accessible from the internet
  • Ensuring that all ports are protected by firewalls, especially the MongoDB port (27017 by default).
  • Only allowing access to the https port (443 by default) if required

Entradas populares de este blog

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...
Leer más

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

How To Add a Custom Selector for the Screen Field

Fuente original del artículo:   https://www.rklesolutions.com/blog/how-to-add-a-custom-selector-for-the-screen-field January 5, 2022 By RKL Team Leave a Comment There may be times when you want to add a pop-up window to select a field for a screen. Sometimes this can be handled automatically if the field is a standard X3 object field (i.e. when selecting a product with a type of ITM from the ITMMASTER table). There may be other times where a standard look-up is not available, and some custom code is required to do the selection window. We'll show you how to add a custom selector of your choosing to the screen field. ADD SELECT ON SCREEN FIELD The first step is to add the appropriate code to the field on the screen in Sage X3: Go to  Development > Script Dictionary > Screens Select Your Screen Select the field to have the lookup for  by moving your cursor to it on the screen. The field should show with a blue background. Select a type of "Selection" , and an  ac...
Leer más