dbcve.org
Romepi FirmwareOperating system · Amd

CVE-2021-46767

MEDIUM · 6.1 CVSS v3.1 Published 2023-01-11
Fix available
A fix is available. Upgrade to 1.0.0.d / 1.0.0.6 or later.
See remediation →
66/100
Remediation priority · Elevated
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
Insufficient input validation in the ASP may allow an attacker with physical access, unauthorized write access to memory potentially leading to a loss of integrity or denial of service.

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

Insufficient input validation in ASP (Active Server Pages) could allow an attacker with physical access to perform unauthorized memory writes, potentially compromising data integrity or causing a denial of service condition.

MitigationApply available vendor patches for the affected ASP components and implement rigorous input validation controls to prevent unauthorized memory access.

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
Romepi FirmwareOperating system
Affected:< 1.0.0.d
Milanpi FirmwareOperating system
Affected:< 1.0.0.6

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

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/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. Identify if the system uses AMD Romepi or Milanpi platform
    Check the server hardware platform via dmidecode -s system-product-name, or check BMC/IPMI for platform information, or inspect /sys/class/dmi/id/product_name
    Affected if The platform is AMD Romepi or AMD Milanpi
  2. Determine the ASP firmware version on Romepi
    Use the platform's firmware version command or check BMC firmware inventory for the ASP component version. Typical commands: ipmitool raw command, or check /usr/local/bin/amd-asp version, or review firmware update logs
    Affected if The installed ASP firmware version is less than 1.0.0.d (for Romepi systems)
  3. Determine the ASP firmware version on Milanpi
    Use the platform's firmware version command or check BMC firmware inventory for the ASP component version. Typical commands: ipmitool raw command, or check /usr/local/bin/amd-asp version, or review firmware update logs
    Affected if The installed ASP firmware version is less than 1.0.0.6 (for Milanpi systems)
  4. Confirm physical access requirement
    Verify that the system could be accessed physically by unauthorized personnel, or review physical security controls on the server enclosure and BMC access
    Affected if Physical access to the system is possible without additional security controls

The system is affected if it runs AMD Romepi firmware below 1.0.0.d or AMD Milanpi firmware below 1.0.0.6, and an attacker could gain physical access to perform the unauthorized memory writes through insufficient input validation in the ASP component.

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 1.0.0.d / 1.0.0.6 or later
Fixed in 1.0.0.d1.0.0.6
Interim mitigation

Apply available vendor patches for the affected ASP components and implement rigorous input validation controls to prevent unauthorized memory access.

Recommended fix High confidence

Romepi: firmware >= 1.0.0.d | Milanpi: firmware >= 1.0.0.6

  1. Identify the specific AMD processor platform (Romepi or Milanpi) in your environment
  2. Locate the current firmware version running on the affected processor
  3. For Romepi systems: Upgrade firmware to version 1.0.0.d or later
  4. For Milanpi systems: Upgrade firmware to version 1.0.0.6 or later
  5. Verify the firmware upgrade was successful by confirming the new version post-update
  6. Ensure the upgrade process follows AMD's recommended firmware update procedure for the specific platform

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

Fix this in Romepi Firmware 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-2021-46767 — 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-2021-46767 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