dbcve.org
Mercedes MeApplication · Mercedes Benz

CVE-2023-47392

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-22
Fix available
A fix is available. Upgrade to after 1.34.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
An access control issue in Mercedes me IOS APP v1.34.0 and below allows attackers to view the carts of other users via sending a crafted add order request.

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

This is an Insecure Direct Object Reference (IDOR) vulnerability in the Mercedes me iOS APP where the add order API endpoint lacks proper authorization checks. Attackers can view other users' carts by manipulating order/cart identifiers in crafted requests, indicating broken access control at the API layer.

MitigationImplement server-side authorization validation to ensure users can only access their own cart/order data. All API endpoints returning user-specific data must verify the authenticated user matches the requested resource owner.

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
Mercedes MeApplication
Affected:<= 1.34.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
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Mercedes Me app version on iOS device
    Open the App Store, search for Mercedes Me, or go to Settings > General > iPhone Storage (or Apps) > Mercedes Me to view the installed version number
    Affected if The installed version is 1.34.0 or any earlier version (e.g., 1.33.0, 1.30.0, etc.)
  2. Identify the API endpoint behavior
    Use a network proxy (e.g., Burp Suite, Charles Proxy) to intercept traffic between the Mercedes Me app and its backend while placing an order or viewing cart data
    Affected if The app makes API requests to endpoints related to orders/carts (such as /order, /cart, or /addOrder) without including proper user ownership validation in the request headers or body
  3. Test for IDOR by manipulating identifiers
    Modify the order ID or cart ID in captured API requests to a different numeric or alphanumeric identifier while keeping the same session/authentication token
    Affected if The API returns cart or order data belonging to a different user when the identifier is changed, indicating broken access control
  4. Verify authorization headers are insufficient
    Compare API requests with and without modified identifiers while keeping authentication cookies or tokens unchanged
    Affected if The server returns successful HTTP responses (200 OK) with other users' order/cart data using only valid authentication but without verifying resource ownership

The user is affected if they have Mercedes Me app version 1.34.0 or earlier installed and the backend API lacks proper ownership validation, allowing unauthorized access to other users' cart/order data through identifier manipulation.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.34.0
Interim mitigation

Implement server-side authorization validation to ensure users can only access their own cart/order data. All API endpoints returning user-specific data must verify the authenticated user matches the requested resource owner.

Recommended fix Moderate confidence

Version higher than 1.34.0 (latest version available in the App Store)

  1. Upgrade the Mercedes Me iOS application to the latest version available in the Apple App Store to remediate the access control vulnerability
  2. After updating, verify that the application no longer allows viewing other users' carts through crafted requests
  3. If automatic updates are enabled, ensure the device has automatically received the latest app version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mercedes Me Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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