Lifetime Management ConsoleApplication · Outsystems

CVE-2021-29357

HIGH · 8.6 CVSS v3.1 Published 2021-04-12
Fix available
A fix is available. Upgrade to 10.0.1104.0 / 11.7.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The ECT Provider component in OutSystems Platform Server 10 before 10.0.1104.0 and 11 before 11.9.0 (and LifeTime management console before 11.7.0) allows SSRF for arbitrary outbound HTTP requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The ECT Provider component in OutSystems Platform Server 10 before 10.0.1104.0 and 11 before 11.9.0 (and LifeTime management console before 11.7.0) contains a Server-Side Request Forgery (SSRF) vulnerability that allows attackers to make arbitrary outbound HTTP requests from the server.

MitigationUpgrade OutSystems Platform Server to version 10.0.1104.0 or later (10.x) and 11.9.0 or later (11.x), and LifeTime to 11.7.0 or later. Additionally, restrict outbound network access from server-tier systems to minimize impact if exploitation occurs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Lifetime Management ConsoleApplication
Affected:>= 11, < 11.7.0
OutsystemsApplication
Affected:>= 10, < 10.0.1104.0
Platform ServerApplication
Affected:>= 11, < 11.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check OutSystems Platform Server 10 version
    Locate the installed version of OutSystems Platform Server 10 (x) through the Service Center admin interface, installation logs, or system information. Look for a version number in the format 10.0.xxxx.
    Affected if The version is lower than 10.0.1104.0 (for example, 10.0.828.0 or any 10.0.x version below 10.0.1104.0).
  2. Check OutSystems Platform Server 11 version
    Locate the installed version of OutSystems Platform Server 11 through the Service Center admin interface, installation logs, or system information. Look for a version number in the format 11.x.xxx.
    Affected if The version is lower than 11.9.0 (for example, 11.6.0 or any 11.x version below 11.9.0).
  3. Check LifeTime management console version
    Locate the installed version of the LifeTime management console through the LifeTime console interface, installation logs, or system information. This is typically deployed separately from the Platform Server.
    Affected if The LifeTime version is lower than 11.7.0 (for example, 11.5.0 or any 11.x version below 11.7.0).
  4. Verify ECT Provider component status
    Check whether the ECT (Enterprise Component Toolkit) Provider component is enabled or configured in the OutSystems environment. This can be verified through the Service Center administration console under the relevant module or component settings.
    Affected if The ECT Provider component is present and enabled in the OutSystems environment (the vulnerability only affects systems where this component is configured).

You are affected if any OutSystems Platform Server 10 instance is below 10.0.1104.0, any Platform Server 11 instance is below 11.9.0, or any LifeTime console is below 11.7.0, and the ECT Provider component is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 10.0.1104.0 / 11.7.0 / 11.9.0 or later
Fixed in 10.0.1104.011.7.011.9.0
Interim mitigation

Upgrade OutSystems Platform Server to version 10.0.1104.0 or later (10.x) and 11.9.0 or later (11.x), and LifeTime to 11.7.0 or later. Additionally, restrict outbound network access from server-tier systems to minimize impact if exploitation occurs.

Fix this in Lifetime Management Console Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-29357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-29357 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data