dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-0067

MEDIUM · 6.3 CVSS v3.1 Published 2025-01-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
Due to a missing authorization check on service endpoints in the SAP NetWeaver Application Server Java, an attacker with standard user role can create JCo connection entries, which are used for remote function calls from or to the application server. This could lead to low impact on confidentiality, integrity, and availability of the application.

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 · moderate confidence

Missing authorization check on service endpoints in SAP NetWeaver Application Server Java allows standard users to create JCo (Java Connector) connection entries. These JCo connections are used for RFC (Remote Function Call) communication to and from the application server, potentially enabling unauthorized outbound or inbound connections to external systems.

MitigationApply the SAP security note/patch for CVE-2025-0067 to implement proper authorization checks on JCo service endpoints. Additionally, review and restrict user role assignments to ensure only authorized administrators have permissions to create or modify JCo connections.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 SAP NetWeaver AS Java installation
    Check system for SAP NetWeaver Application Server Java components. Look for Java processes related to SAP J2EE engine or use transaction SM51 (if available) to list server instances.
    Affected if The system is running SAP NetWeaver Application Server Java.
  2. Determine installed NetWeaver Java version
    Use SAP transaction SM37 or check the SAP kernel version. Compare your version against the supported versions for your SAP patch level. Alternatively, check the SAPMMC or SAP Control for the AS Java version string.
    Affected if The installed version has not received the CVE-2025-0067 patch.
  3. Verify JCo (Java Connector) module is active
    Check if JCo functionality is configured in the SAP NetWeaver AS Java. Look for JCo-related services in the SAP System Landscape Directory (SLD) or check the J2EE cluster configuration for active JCo destinations.
    Affected if JCo module is enabled and JCo connection destinations exist in the system.
  4. Review user roles for JCo connection creation rights
    Examine SAP user role assignments using transaction PFCG or SUIM. Specifically look for standard (non-administrative) users that may have roles containing permissions to create or modify JCo destinations (often under the SAP_JCO_FUNCTION or equivalent JCo-related authorization objects).
    Affected if Standard users have roles allowing creation or modification of JCo connections.
  5. Inspect existing JCo destination configurations
    Use transaction SALE or SM59 (for RFC destinations) to view JCo connection configurations. Check the created JCo destinations to identify any that were created by non-administrative users.
    Affected if JCo connections exist that were created by standard users without proper admin authorization.

A system is affected if it runs SAP NetWeaver AS Java with JCo enabled and has standard users with permissions to create or modify JCo connections without proper authorization checks.

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 SAP security note/patch for CVE-2025-0067 to implement proper authorization checks on JCo service endpoints. Additionally, review and restrict user role assignments to ensure only authorized administrators have permissions to create or modify JCo connections.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0067 — 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-0067 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