A vulnerability was reported against SSL.com, a Certificate Authority (CA), allowing fraudulent issuance of SSL certificates for arbitrary MX hostnames. Their domain control validation (DCV) process was flawed: by setting specific TXT records, an attacker could bypass verification checks and obtain certificates for domains they didn't own, potentially enabling man-in-the-middle attacks. SSL.com confirmed and addressed the issue, revoking the fraudulently issued certificates. Mozilla subsequently added SSL.com to their CA incident database.
GPS jamming and spoofing are increasing threats to aircraft navigation, with potentially dangerous consequences. A new type of atomic clock, much smaller and cheaper than existing ones, could provide a highly accurate backup navigation system, independent of vulnerable satellite signals. These chip-scale atomic clocks (CSACs), while not yet widespread, could be integrated into aircraft systems to maintain precise positioning and timing even when GPS signals are lost or compromised, significantly improving safety and resilience.
HN commenters discuss the plausibility and implications of GPS spoofing for aircraft. Several express skepticism that widespread, malicious spoofing is occurring, suggesting alternative explanations for reported incidents like multipath interference or pilot error. Some point out that reliance on GPS varies among aircraft and that existing systems can mitigate spoofing risks. The potential vulnerabilities of GPS are acknowledged, and the proposed atomic clock solution is discussed, with some questioning its cost-effectiveness and complexity compared to other mitigation strategies. Others suggest that focusing on improving the resilience of GPS itself might be a better approach. The possibility of state-sponsored spoofing is also raised, particularly in conflict zones.
This post showcases a "lenticular" QR code that displays different content depending on the viewing angle. By precisely arranging two distinct QR code patterns within a single image, the creator effectively tricked standard QR code readers. When viewed head-on, the QR code directs users to the intended, legitimate destination. However, when viewed from a slightly different angle, the second, hidden QR code becomes readable, redirecting the user to an "adversarial" or unintended destination. This demonstrates a potential security vulnerability where malicious QR codes could mislead users into visiting harmful websites while appearing to link to safe ones.
Hacker News commenters discuss various aspects of the QR code attack described, focusing on its practicality and implications. Several highlight the difficulty of aligning a camera perfectly to trigger the attack, suggesting it's less a realistic threat and more a clever proof of concept. The potential for similar attacks using other mediums, such as NFC tags, is also explored. Some users debate the definition of "adversarial attack" in this context, arguing it doesn't fit the typical machine learning definition. Others delve into the feasibility of detection, proposing methods like analyzing slight color variations or inconsistencies in the printing to identify manipulated QR codes. Finally, there's a discussion about the trust implications and whether users should scan QR codes displayed on potentially compromised surfaces like public screens.
Summary of Comments ( 58 )
https://news.ycombinator.com/item?id=43738485
Hacker News commenters discuss the severity and implications of the SSL.com vulnerability, with some downplaying its impact due to the requirement of compromising an email account first. Several highlight the unusual nature of DCV through email, questioning its security compared to other methods like DNS or HTTP. The discussion also touches on the complexities of certificate issuance and the potential for abuse, with one commenter suggesting the core issue lies in the CA's trust and the difficulty of verifying domain ownership reliably. Others point out that this vulnerability isn't new and express frustration with the slow response from CAs. The conversation also drifts towards the broader issue of CA trust and the need for better systems, with some suggesting decentralized solutions. Finally, a few comments mention the irony of a security company like SSL.com having such a vulnerability.
The Hacker News post titled "Ssl.com: DCV bypass and issue fake certificates for any MX hostname" (https://news.ycombinator.com/item?id=43738485) has several comments discussing the implications of the vulnerability described in the linked Bugzilla report.
Several commenters express surprise and concern over the severity of the vulnerability, allowing the issuance of fake certificates for arbitrary MX hostnames. One commenter highlights the potential for significant damage, noting that email servers could be impersonated, leading to interception of sensitive information. The ease with which the vulnerability could be exploited is also mentioned, emphasizing the risk it posed.
The discussion delves into the technical details of the vulnerability, with commenters explaining how the Domain Control Validation (DCV) process was bypassed. Specifically, the comments mention how ssl.com's system misinterpreted specific responses, allowing an attacker to claim control over a domain they didn't own. The conversation also touches upon the complexities of properly implementing and securing the various DCV methods.
Some commenters question the responsibility of Certificate Authorities (CAs) in preventing such vulnerabilities, suggesting more rigorous checks and validation procedures. The impact on trust in the certificate ecosystem is also a point of discussion, with concerns raised about the potential erosion of user confidence in online security.
One commenter questions the response time and transparency of ssl.com in addressing the issue. Others speculate on the potential motivations and technical capabilities of actors who might exploit such a vulnerability.
The comments also explore the broader implications for email security and the challenges of maintaining a secure online environment in the face of constantly evolving threats. The vulnerability is framed within the context of larger systemic issues surrounding digital certificate issuance and validation.