dbcve.org
Mobile Application PlatformApplication · Redhat

CVE-2017-7552

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-29
Fix available
A fix is available. Upgrade to after 4.4.3 or later.
See remediation →
100/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
A flaw was discovered in the file editor of millicore, affecting versions before 3.19.0 and 4.x before 4.5.0, which allows files to be executed as well as created. An attacker could use this flaw to compromise other users or teams projects stored in source control management of the RHMAP Core installation.

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

A critical vulnerability in millicore's file editor allows attackers to execute arbitrary files rather than just create them. This enables remote code execution within the RHMAP Core installation, potentially compromising the source control management system and affecting multiple users and teams.

MitigationUpgrade millicore to version 3.19.0 or later, or 4.5.0 or later for the 4.x branch. If immediate upgrading is not possible, disable or restrict access to the file editor component until the patch can be applied.

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
Mobile Application PlatformApplication
Affected:<= 4.4.3

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 RHMAP Core installation
    Identify if Redhat Mobile Application Platform is installed in your environment. Check for millicore service/process running.
    Affected if Redhat Mobile Application Platform is present and millicore component is active
  2. Check millicore version
    Determine the installed version of the millicore component. Compare against affected versions: <= 4.4.3
    Affected if millicore version is 4.4.3 or earlier, or version is unknown and falls within the 4.x branch <= 4.4.3
  3. Verify file editor is accessible
    Check if the file editor component is enabled and accessible within the RHMAP Core installation. Inspect access controls and component status.
    Affected if File editor component is enabled and exposed to users or network access
  4. Check file editor configuration
    Review the file editor configuration settings for restrictions on file operations. Look for settings that control execute versus create permissions.
    Affected if File editor permits execution of arbitrary files or lacks restrictions on file type/operation limits

Your environment is affected if Redhat Mobile Application Platform with millicore version 4.4.3 or earlier is running with the file editor component enabled and accessible.

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 4.4.3
Interim mitigation

Upgrade millicore to version 3.19.0 or later, or 4.5.0 or later for the 4.x branch. If immediate upgrading is not possible, disable or restrict access to the file editor component until the patch can be applied.

Recommended fix High confidence

4.5.0 (for 4.x branch) or 3.19.0 (for 3.x branch)

  1. Backup all current data and configuration of the Mobile Application Platform installation
  2. Identify the current version branch (3.x or 4.x) of the installation
  3. If running 4.x branch: upgrade to version 4.5.0 or later
  4. If running 3.x branch: upgrade to version 3.19.0 or later
  5. After upgrade, verify the millicore component has been updated to the fixed version
  6. Test the file editor functionality to confirm the vulnerability is remediated
  7. Review audit logs for any suspicious file execution activity that may have occurred prior to the patch
Caveat Review release notes for 4.5.0/3.19.0 for any potential compatibility issues with existing integrations or dependencies

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

Fix this in Mobile Application Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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