dbcve.org
Traffic ServerApplication · Apache

CVE-2018-9481

MEDIUM · 6.5 CVSS v3.1 Published 2024-11-20
Fix available
A fix is available. Upgrade to 7.1.10 / 8.0.7 or later.
See remediation →
70/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
In bta_hd_set_report_act of bta_hd_act.cc, there is a possible out-of-bounds read due to an integer overflow. This could lead to remote information disclosure in the Bluetooth service with no additional execution privileges needed. User interaction is not needed for exploitation.

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

An integer overflow vulnerability exists in the bta_hd_set_report_act function in bta_hd_act.cc within the Bluetooth HID (Human Interface Device) component. The overflow enables an out-of-bounds read, allowing remote information disclosure via the Bluetooth service without requiring additional privileges or user interaction.

MitigationApply vendor security patches for this vulnerability; Android users should install the latest Google security bulletin updates. Until patches are available, minimize Bluetooth exposure by disabling Bluetooth when not in use.

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
Traffic ServerApplication
Affected:>= 6.0.0, <= 6.2.3>= 7.0.0, < 7.1.10>= 8.0.0, < 8.0.7
AndroidOperating system
Affected:= 8.0= 8.1= 9.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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/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. Identify if Apache Traffic Server is installed
    Check for the presence of the 'trafficserver' binary or package using 'which trafficserver' or 'dpkg -l | grep trafficserver' (Debian) / 'rpm -qa | grep trafficserver' (RHEL)
    Affected if Apache Traffic Server is installed and the version falls within >= 6.0.0, <= 6.2.3; >= 7.0.0, < 7.1.10; or >= 8.0.0, < 8.0.7
  2. Confirm Bluetooth HID component is in use
    For Android, check if Bluetooth HID profile is enabled by examining system logs during Bluetooth HID device connection, or verify Bluetooth is actively used on the device
    Affected if Bluetooth is enabled and the device uses Bluetooth HID functionality (keyboards, mice, game controllers) on affected Android versions

A system is affected if it runs Apache Traffic Server in any of the listed version ranges, or runs Google Android versions 8.0, 8.1, or 9.0 with Bluetooth HID functionality enabled.

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 7.1.10 / 8.0.7 or later
Fixed in 7.1.108.0.7
Interim mitigation

Apply vendor security patches for this vulnerability; Android users should install the latest Google security bulletin updates. Until patches are available, minimize Bluetooth exposure by disabling Bluetooth when not in use.

Recommended fix Moderate confidence

Traffic Server: 7.1.10+ or 8.0.7+ (or latest stable 9.x); Android: October 2018 security patch or later

  1. For Traffic Server: Check current version using 'traffic_server -V' or 'tsversion'
  2. For Traffic Server: If running 6.0.0-6.2.3, upgrade to version 7.1.10 or later (7.x LTS)
  3. For Traffic Server: If running 7.0.0-7.1.9, upgrade to version 7.1.10 or later
  4. For Traffic Server: If running 8.0.0-8.0.6, upgrade to version 8.0.7 or later
  5. For Android: Apply the appropriate Android monthly security patch level (SPL) from Google or your device manufacturer
  6. For Android: Verify the fix via Settings > About Phone > Android security patch level
Caveat Traffic Server major version upgrades may require configuration or plugin compatibility review

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

Fix this in Traffic Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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