dbcve.org
Production Planning And ControlApplication · Sap

CVE-2013-3062

MEDIUM · 6.5 CVSS v2.0 Published 2013-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/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
The CP_RC_TRANSACTION_CALL_BY_SET function in the Engineering Workbench component in SAP Production Planning and Control allows remote authenticated users to bypass intended transaction restrictions via unspecified vectors.

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

The CP_RC_TRANSACTION_CALL_BY_SET function in SAP's Engineering Workbench component (Production Planning and Control) fails to properly enforce transaction authorization restrictions. Authenticated users can bypass intended access controls and execute transactions they should not have permission to access.

MitigationApply SAP security patches for CVE-2013-3062 and review transaction authorization assignments in the Engineering Workbench to ensure proper restriction enforcement.

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
Production Planning And ControlApplication
Affected:all versions

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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. Identify SAP system version and release
    Execute SAP transaction SM51 or use SAPMSSQL to query the system version information. Record the SAP ERP release version and patch level.
    Affected if The system is running any version of SAP ERP with the Production Planning and Control module (Engineering Workbench) installed.
  2. Confirm Engineering Workbench component is active
    Check if transaction code SE80 or related PP (Production Planning) transactions are accessible in the system. Query table TADIR for objects in the Engineering Workbench namespace.
    Affected if The Engineering Workbench component (namespace related to Production Planning and Control) is installed and accessible in the system.
  3. Verify CP_RC_TRANSACTION_CALL_BY_SET function module exists
    Use transaction SE37 (Function Builder) or query table TFDIR to search for function module CP_RC_TRANSACTION_CALL_BY_SET. Check its source code for authorization checks.
    Affected if The function module CP_RC_TRANSACTION_CALL_BY_SET exists without proper transaction authorization enforcement in its code logic.
  4. Review transaction authorization configuration
    Use transaction SUIM (User Information System) or SU53 to analyze transaction code authorization assignments for test user accounts. Compare assigned transactions against intended restrictions.
    Affected if Authenticated users can access transaction codes that are not explicitly assigned to their role profile.
  5. Test authorization bypass capability
    Using a low-privilege authenticated user account, attempt to execute restricted transactions through the Engineering Workbench function module CP_RC_TRANSACTION_CALL_BY_SET.
    Affected if Users can execute transaction codes they should not have permission to access through the vulnerable function.

The environment is affected if the Engineering Workbench component is installed and the CP_RC_TRANSACTION_CALL_BY_SET function allows authenticated users to bypass transaction authorization restrictions.

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 SAP security patches for CVE-2013-3062 and review transaction authorization assignments in the Engineering Workbench to ensure proper restriction enforcement.

Fix this in Production Planning And Control Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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