Headline
CVE-2022-29849: OpenEdge Application Development | Progress OpenEdge
In Progress OpenEdge before 11.7.14 and 12.x before 12.2.9, certain SUID binaries within the OpenEdge application were susceptible to privilege escalation. If exploited, a local attacker could elevate their privileges and compromise the affected system.
OpenEdge 12 Series:
Modernization is the Destination.
Your Journey Starts Here.
What’s New in OpenEdge 12.5?
Our newest release is now available. Here are a list of the new features you’ll want to check out.
Why OpenEdge
It’s reliability, cost-effectiveness and focus on addressing evolving demands, continues to make Progress OpenEdge a wise investment.
Forrester Consulting Study—The Total Economic Impact™ of Progress OpenEdge 12 Series
Total Economic Impact™ study quantifies substantial Partner ROI from OpenEdge 12 Series.
Choose Your Path to Application Modernization
OpenEdge offers a choice when it comes to modernizing your application. It continues to address the need to evolve your business by delivering applications that are highly-available, high performing and agile. Supporting your need to address the demands of your customers and users today and tomorrow, the Progress Application Evolution approach provides measured steps towards modernization that eliminate the need for re-architecting. Take a moment to discover what OpenEdge 12 can do for your business.
Available
Significant database uptime enhancements to deliver closer to the demands of Five 9’s.
Powerful
Improve monitoring of performance and availability through new DevOps tooling.
Secure
Continuous security improvements to help you operate with minimal risk of compromise.
Agile
Combine OpenEdge functionality with AWS Cloud services.
Hear from OpenEdge Users About Their
Business Evolution
We are particularly excited about its performance and ability to truly scale. We’re glad to have it in our production environment, especially for our larger customers.
Ken Walsh Product Manager Constellation Financing Systems Learn more Read Case Study
Most businesses are turning towards a business-to-consumer experience, and that is what both employees and managers are expecting.
Morten Janum CIO and Vice President, Mark Information Learn more Read Case Study
We didn’t want to use the production database for reporting and all the integrations with other applications. We needed something that would alleviate stress from the production database. Pro2 was exactly what we were looking for.
Izabella Legocka Director of IT Applications at Turtle & Hughes Learn more Read Case Study
Partners for Success
Progress offers many programs and expert services to partner with you for success.
Progress by the Numbers
5,000+
Business Applications
6,000,000+
Application Users
Database Trends and Applications Trend Setting Product for 2020
Progress OpenEdge was chosen by Database Trends and Applications as a trend setting product in Data and Information Management; recognized in helping organizations derive greater benefit from their data, make decisions faster, and do so with higher levels of security.
Frost and Sullivan Best Practices Award for 2020
Modernizing to the latest OpenEdge version will help you leverage new technologies while protecting the equity and familiarity of the OpenEdge codebase. Organizations can use the breadth of the Progress portfolio to realize “40% reduction in time-to-market for business-critical apps and a 60% reduction in app development and deployment costs.”
Learning & Resources
Progress OpenEdge 12 Series
Your Application Evolution Journey Starts Here
Related news
The RSS extension before 2022-04-29 for MediaWiki allows XSS via an rss element (if the feed is in $wgRSSUrlWhitelist and $wgRSSAllowLinkTag is true).
nopCommerce 4.50.1 is vulnerable to Directory Traversal via the backup file in the Maintenance feature.
Cyclos 4 PRO 4.14.7 and before does not validate user input at error inform, which allows remote unauthenticated attacker to execute javascript code via undefine enum constant.
A Dom-based Cross-site scripting (XSS) vulnerability at registration account in Cyclos 4 PRO.14.7 and before allows remote attackers to inject arbitrary web script or HTML via the groupId parameter.
All versions of package jsgui-lang-essentials are vulnerable to Prototype Pollution due to allowing all Object attributes to be altered, including their magical attributes such as proto, constructor and prototype.
All versions of package jailed are vulnerable to Sandbox Bypass via an exported alert() method which can access the main application. Exported methods are stored in the application.remote object.
All versions of package dset are vulnerable to Prototype Pollution via 'dset/merge' mode, as the dset function checks for prototype pollution by validating if the top-level path contains __proto__, constructor or protorype. By crafting a malicious object, it is possible to bypass this check and achieve prototype pollution.
All versions of package masuit.tools.core are vulnerable to Arbitrary Code Execution via the ReceiveVarData<T> function in the SocketClient.cs component. The socket client in the package can pass in the payload via the user-controllable input after it has been established, because this socket client transmission does not have the appropriate restrictions or type bindings for the BinaryFormatter.
The package angular after 1.7.0 are vulnerable to Regular Expression Denial of Service (ReDoS) by providing a custom locale rule that makes it possible to assign the parameter in posPre: ' '.repeat() of NUMBER_FORMATS.PATTERNS[1].posPre with a very high value. **Note:** 1) This package has been deprecated and is no longer maintained. 2) The vulnerable versions are 1.7.0 and higher.
The package dexie before 3.2.2, from 4.0.0-alpha.1 and before 4.0.0-alpha.3 are vulnerable to Prototype Pollution in the Dexie.setByKeyPath(obj, keyPath, value) function which does not properly check the keys being set (like __proto__ or constructor). This can allow an attacker to add/modify properties of the Object.prototype leading to prototype pollution vulnerability. **Note:** This vulnerability can occur in multiple ways, for example when modifying a collection with untrusted user input.
All versions of package com.bstek.ureport:ureport2-console are vulnerable to Remote Code Execution by connecting to a malicious database server, causing arbitrary file read and deserialization of local gadgets.
All versions of package materialize-css are vulnerable to Cross-site Scripting (XSS) due to improper escape of user input (such as <not-a-tag />) that is being parsed as HTML/JavaScript, and inserted into the Document Object Model (DOM). This vulnerability can be exploited when the user-input is provided to the autocomplete component.
The package s-cart/s-cart before 6.9; the package s-cart/core before 6.9 are vulnerable to Cross-site Scripting (XSS) which can lead to cookie stealing of any victim that visits the affected URL so the attacker can gain unauthorized access to that user's account through the stolen cookie.
This affects all versions of package libxmljs. When invoking the libxmljs.parseXml function with a non-buffer argument the V8 code will attempt invoking the .toString method of the argument. If the argument's toString value is not a Function object V8 will crash.
The package git-pull-or-clone before 2.0.2 are vulnerable to Command Injection due to the use of the --upload-pack feature of git which is also supported for git clone. The source includes the use of the secure child process API spawn(). However, the outpath parameter passed to it may be a command-line argument to the git clone command and result in arbitrary command injection.
The package com.google.code.gson:gson before 2.8.9 are vulnerable to Deserialization of Untrusted Data via the writeReplace() method in internal classes, which may lead to DoS attacks.
All versions of package com.alibaba.oneagent:one-java-agent-plugin are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip) using a specially crafted archive that holds directory traversal filenames (e.g. ../../evil.exe). The attacker can overwrite executable files and either invoke them remotely or wait for the system or user to call them, thus achieving remote command execution on the victim’s machine.
The package sqlite3 before 5.0.3 are vulnerable to Denial of Service (DoS) which will invoke the toString function of the passed parameter. If passed an invalid Function object it will throw and crash the V8 engine.
The package convict before 6.2.2 are vulnerable to Prototype Pollution via the convict function due to missing validation of parentKey. **Note:** This vulnerability derives from an incomplete fix of another [vulnerability](https://security.snyk.io/vuln/SNYK-JS-CONVICT-1062508)