dbcve.org
Tetra Connectivity ServerApplication · Airbus

CVE-2025-7024

HIGH · 7.3 CVSS v3.1 Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

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
Incorrect Default Permissions vulnerability in AIRBUS PSS TETRA Connectivity Server on Windows Server OS allows Privilege Abuse. An attacker may execute arbitrary code with SYSTEM privileges if a user is tricked or directed to place a crafted file into the vulnerable directory. This issue affects TETRA connectivity Server: 7.0. Vulnerability fix is available and delivered to impacted customers.

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

AIRBUS PSS TETRA Connectivity Server 7.0 on Windows Server OS ships with overly permissive default file system permissions, allowing a local attacker to place malicious files in a vulnerable directory. When these files are executed (either through user interaction or automated processes), they run with SYSTEM privileges, enabling full compromise of the server.

MitigationApply the vendor-provided security patch for TETRA Connectivity Server 7.0 and verify that file/directory permissions are restricted to least-privilege principles, removing any unnecessary write access for non-privileged users.

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
Tetra Connectivity ServerApplication
Affected:= 7.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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Confirm Airbus Tetra Connectivity Server version
    Check installed version via Windows Registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or inspect Program Files for 'Airbus' or 'Tetra' folders. Run 'wmic product get name,version' if available.
    Affected if Version displayed is exactly 7.0
  2. Identify the TETRA Connectivity Server service
    Open Services console (services.msc) and locate the service named 'TETRA Connectivity Server' or similar. Right-click and select Properties.
    Affected if Service exists and is installed on the system
  3. Verify service runs with SYSTEM privileges
    In the service Properties, check the 'Log on as' field. Confirm it is set to 'Local System account' or 'NT AUTHORITY\SYSTEM'.
    Affected if Service runs as Local System or SYSTEM account
  4. Identify the service executable and its working directories
    In service Properties, note the 'Path to executable'. Use Process Explorer or sc queryex to find the process, then use Process Monitor to identify directories the service accesses during operation.
    Affected if Service accesses a directory accessible to unprivileged users
  5. Check file permissions on the service-accessed directory
    Right-click the identified directory in Windows Explorer, go to Security tab, and review permissions. Use 'icacls directory_path' from command prompt to list effective permissions for standard users.
    Affected if Non-admin or Users group has Write or CreateFiles permission to the directory
  6. Test unprivileged file placement
    As a standard user (non-admin), attempt to create a test .exe or .dll file in the identified directory using command prompt or File Explorer.
    Affected if File creation succeeds without admin rights

If the installed version is exactly 7.0 AND the service runs as SYSTEM AND unprivileged users can write files to a directory that the service processes, the environment is affected by this privilege escalation vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided security patch for TETRA Connectivity Server 7.0 and verify that file/directory permissions are restricted to least-privilege principles, removing any unnecessary write access for non-privileged users.

Fix this in Tetra Connectivity Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2025-7024 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