5.3

CVE-2025-43803 IDOR vulnerable in Contacts Center

Description

Insecure direct object reference (IDOR) vulnerability in the Contacts Center widget in Liferay Portal and Liferay DXP allows remote attackers to view contact information, including the contact’s name and email address, via the _com_liferay_contacts_web_portlet_ContactsCenterPortlet_entryId parameter.

Severity

5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)

Affected Version(s)

  • Liferay Portal 7.4.0 through 7.4.3.119
  • Liferay DXP 2023.Q4.0 through 2023.Q4.6
  • Liferay DXP 2023.Q3.1 through 2023.Q3.10
  • Liferay DXP 7.4 GA through U92
  • Liferay DXP 7.3, and older unsupported versions

Fixed Version(s)

 

Acknowledgments

This issue was reported by foobar7

Publication Date: 

de novembre 11, 2024

Found a Bug?

Now that we have all of our code ready, we are ready to deploy it to our Liferay instance. How? First we have to build the application. We will do this by running the following command

yarn build

 

in the application root folder (for explanation on why I am using yarn instead of npm check this blog). This will generate a “build” folder and inside it there will be a “static” folder. In this folder there will be the transpiled css and js files that we need to deploy to our Liferay instance. Specifically, we will need the files that have a name format such as main.abc123.js and main.cde456.css. We are going to take these two files and upload them to Liferay’s document library.

With our code in Liferay now we can register our Remote App. To do this, we’ll access the Remote apps menu by accessing the applications tab (clicking on the top right dotted square). From here, we’ll add a new Remote App named “Search map”. We’ll choose “custom element” as its type, use the same ID we gave our application in the code (search-map-app) as the HTML element name and add the URLs to our JS and CSS files in the URL and CSS URL fields respectively. Since we have this code in Liferay’s document library we can get this URL by clicking on the file, then on the top right information icon and copying the Latest Version URL.

However, in a real production environment these files should be hosted on a server optimized for hosting static resources (in this case you will also have to enable CORS, to do so you can check Liferay's documentation).

 

The final configuration will look like this:

With this done we can add our application to any content page we want. This is achieved the same way as with any other fragment or widget: drag and drop.

If you have found, or think you have found a bug, help us to help you by letting us know!

Here we have our React Remote App in Liferay! Now you can play around with it, testing the filters, adding more points or you can even step up the game and try to style the application to make it look more appealing.
 

Advantages of this new development paradigm and final conclusions

As we have seen throughout this blog, with the use of Objects you can avoid having to develop whole Service builder modules to model your data. Furthermore, Objects are integrated with Liferay’s frameworks such as Asset Framework and Permissions Framework, so it makes data modeling much quicker and easier without having to write any code. As a plus, since Objects are totally managed by DXP you won’t have any code you need to upgrade whenever you update your Liferay DXP version.

 

With the Remote Apps approach you can now build applications to use in Liferay with modern technologies,  such as React (our case here), Angular, Vue... Moreover, you can still access Liferay’s services and data thanks to their REST APIs, which are also available with Objects.

 

You can find all the code used in this blog in this repository, plus the Objects’ schemas used in this folder.

 

I hope you find this blog useful for all your future projects with Liferay DXP 7.4. If you have any tips, doubts or suggestions please leave them as a comment below. Thank you for reading this blog!