Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 1.55% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2012
CVE-2012-4687High confidence
Post Oak Bluetooth Traffic Systems Insufficient Entropy
Post Oak Traffic Systems · AWAM Bluetooth Reader Traffic System
7.6HighCVSS 2.0
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Post Oak Traffic Systems AWAM Bluetooth Reader Traffic System and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Post Oak AWAM Bluetooth Reader Traffic System does not use a sufficient source of entropy for private keys, which makes it easier for man-in-the-middle attackers to spoof a device by predicting a key value.
What
Post Oak AWAM Bluetooth Reader Traffic System does not use a sufficient source of entropy for private keys, which makes it easier for man-in-the-middle attackers to spoof a device by predicting a key value.
Why
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
How
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Post Oak AWAM Bluetooth Reader Traffic System does not use a sufficient source of entropy for private keys, which makes it easier for man-in-the-middle attackers to spoof a device by predicting a key value.
Why
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
How
An attacker operating through the affected interface may attempt exploitation when the stated preconditions are met. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- the affected interface → Insufficient Entropy → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Unspecified
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Not stated in the selected CVSS metric
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Not stated in the selected CVSS metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-331 ↗
CWE-331: Insufficient Entropy. The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. AV:N/AC:H/Au:N/C:C/I:C/A:C- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Fixed
- Post Oak has developed a patch for the AWAM Bluetooth Reader Traffic
- System that mitigates the vulnerability. The patch allows the Bluetooth
- reader to ensure sufficient entropy exists before generating host and
- authentication keys. The patch will be installed on all new devices when
- initially configured. Existing equipment will be patched by remote
- access and upgraded to the latest firmware. System owners are encouraged
- to contact Post Oak Traffic Systems,
- support@postoaktraffic.com, (281) 381-2887. with questions patching their systems.
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 8 Dec 2012 · Last source change 9 Jul 2025, 18:27 UTC · CWE-331 · Insufficient Entropy
CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-13
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2012-4612
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2012-4612 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2012-4612"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
CVE published
Fixed release or patch reference recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.