Aggregator
CVE-2022-49119 | Linux Kernel up to 5.10.110/5.15.33/5.16.19/5.17.2 pm8001_chip_fw_flash_update_req memory leak (Nessus ID 234545)
CVE-2022-49107 | Linux Kernel up to 5.10.110/5.15.33/5.16.19/5.17.2 ceph_readdir memory leak (Nessus ID 234545)
CVE-2022-49084 | Linux Kernel up to 5.17.2 qede_build_skb denial of service (Nessus ID 234545)
CVE-2022-49109 | Linux Kernel up to 5.15.33/5.16.19/5.17.2 ceph_get_snapdir privilege escalation (Nessus ID 234545)
The FTC Is Watching: GoDaddy’s Settlement Sends a Clear Message on API Security
In today’s rapidly changing digital environment, APIs play a crucial role in modern business, facilitating smooth connectivity and data sharing. Yet, this interconnected nature brings significant security and privacy risks, as evidenced by the Federal Trade Commission's (FTC) recent settlement with GoDaddy. This settlement serves as a stark reminder that strong API security is no longer just a good security practice but is now a legal obligation.
GoDaddy’s API Security BreachesThe FTC's actions against GoDaddy arose from the company’s failure to implement suitable security measures, which resulted in repeated data breaches between 2019 and 2022. These incidents exposed sensitive customer information, including usernames, passwords, and employee credentials. The FTC’s investigation highlighted several critical API security shortcomings:
- Inadequate API Authentication: One API from GoDaddy compromised sensitive customer data by lacking multi-factor authentication (MFA) and encryption.
- Insufficient API Monitoring: GoDaddy did not implement vital security features such as rate-limiting, logging, and anomaly detection, which allowed unauthorized access to 1.2 million customer records.
- Weak Access Controls: The company's APIs disclosed admin credentials and encryption keys, enabling attackers to compromise websites.
As part of this settlement, the FTC imposed a comprehensive security regimen on GoDaddy, introducing, among other things, various API security requirements. These requirements reflect the FTC’s increased scrutiny of API security and offer a clear structure for businesses to adopt:
- Encrypted API Communications: APIs used for delivering services or involving personally identifiable information (PII) must utilize HTTPS for all requests, with TLS encryption for data in transit.
- Access Control: API requests should be authenticated using a method that safeguards authenticity at the session level and includes adequate protections against session hijacking and information tampering.
- Rate Limiting: API connections must implement suitable rate limiting to guard against abuse and distributed denial-of-service attacks.
- Monitoring & Anomaly Detection: Both inbound and outbound API traffic should be diligently monitored for suspicious activities and attacks.
- Audit Logs & Incident Response: API security logs must be maintained and analyzed to detect and respond to breaches.
The GoDaddy settlement highlights the significant legal and business ramifications that arise from inadequate API security. Companies that neglect API security may face several consequences, including:
- Regulatory Risks: The FTC has shown a readiness to take action against companies with insufficient API security measures. Noncompliance can lead to scrutiny from the FTC, financial penalties, and government oversight.
- Reputation Damage: API security breaches can intrinsically harm a company’s reputation, reducing customer trust and inflicting long-term damage to the brand.
- Operational disruptions: A compromised API can result in data theft, fraud, and service disruptions that affect business continuity and revenue
Salt Security is the foremost API security platform that aids organizations in discovering, protecting, and managing their APIs at scale. The Salt platform offers a full range of capabilities to meet the FTC’s API security requirements, helping organizations develop and maintain a robust API security framework, including:
- API Discovery and Inventory: Automatically identify and catalog all APIs, including shadow APIs, third-party APIs, and legacy systems.
- API Posture Governance: Continuously assess and monitor your APIs’ security posture, delivering insights into potential risks and improvement areas. This includes identifying and mitigating vulnerabilities, enforcing security protocols, and tracking compliance with regulations.
- API Threat Protection: Immediately detect and prevent API attacks, including those from the OWASP Top 10 and complex business logic threats.
- API Vulnerability Management: Spot and address API vulnerabilities before exploitation, including issues linked to authentication, authorization, and data exposure.
- API Compliance: Ensure adherence to regulatory frameworks and standards, such as the API security requirements espoused by the FTC, offering tools and reporting features to validate compliance with security best practices.
By adopting the Salt Security platform, organizations can methodically tackle API security threats, reduce potential legal and business fallout, and protect their digital assets. Schedule a demo to see Salt Security in action.
The post The FTC Is Watching: GoDaddy’s Settlement Sends a Clear Message on API Security appeared first on Security Boulevard.
NIST’s Curved Neutron Beams Could Deliver Benefits Straight to Industry
CISA Adds Three Known Exploited Vulnerabilities to Catalog
CISA has added three new vulnerabilities to its Known Exploited Vulnerabilities Catalog, based on evidence of active exploitation.
- CVE-2025-31200 Apple Multiple Products Memory Corruption Vulnerability
- CVE-2025-31201 Apple Multiple Products Arbitrary Read and Write Vulnerability
- CVE-2025-24054 Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability
These types of vulnerabilities are frequent attack vectors for malicious cyber actors and pose significant risks to the federal enterprise.
Binding Operational Directive (BOD) 22-01: Reducing the Significant Risk of Known Exploited Vulnerabilities established the Known Exploited Vulnerabilities Catalog as a living list of known Common Vulnerabilities and Exposures (CVEs) that carry significant risk to the federal enterprise. BOD 22-01 requires Federal Civilian Executive Branch (FCEB) agencies to remediate identified vulnerabilities by the due date to protect FCEB networks against active threats. See the BOD 22-01 Fact Sheet for more information.
Although BOD 22-01 only applies to FCEB agencies, CISA strongly urges all organizations to reduce their exposure to cyberattacks by prioritizing timely remediation of Catalog vulnerabilities as part of their vulnerability management practice. CISA will continue to add vulnerabilities to the catalog that meet the specified criteria.
CISA Releases Six Industrial Control Systems Advisories
CISA released six Industrial Control Systems (ICS) advisories on April 17, 2025. These advisories provide timely information about current security issues, vulnerabilities, and exploits surrounding ICS.
- ICSA-25-107-01 Schneider Electric Trio Q Licensed Data Radio
- ICSA-25-107-02 Schneider Electric Sage Series
- ICSA-25-107-03 Schneider Electric ConneXium Network Manager
- ICSA-25-107-04 Yokogawa Recorder Products
- ICSA-24-326-04 Schneider Electric Modicon M340, MC80, and Momentum Unity M1E (Update A)
- ICSA-25-058-01 Schneider Electric Communication Modules for Modicon M580 and Quantum Controllers (Update A)
CISA encourages users and administrators to review newly released ICS advisories for technical details and mitigations.
渗透测试手记:从矛盾现象到Oracle注入漏洞的发现之旅
代码审计之实战中各类SQL注入漏洞代码分析及其成因分析(以jeecgboot3.5.3为例)
Seamlessly Integrate ANY.RUN’s Services into Your Infrastructure via SDK
Making ANY.RUN’s products better for the benefit of businesses, organizations, and SOC teams is our top priority. To get maximum value out of our solutions, we provide them with API, a tool enabling users to integrate our services into their security infrastructure. And now, to make this process even smoother, we introduce a software development […]
The post Seamlessly Integrate ANY.RUN’s Services into Your Infrastructure via SDK appeared first on ANY.RUN's Cybersecurity Blog.
Harvest Ransomware Attack: Stolen Data Now Publicly Disclosed
French fintech leader Harvest SAS has become the latest high-profile victim of a sophisticated ransomware attack, culminating this week in the public release of a trove of sensitive stolen data. The breach, orchestrated by the rapidly emerging cybercriminal group known as Run Some Wares, underscores the mounting threats facing financial technology firms and their clients worldwide, as per […]
The post Harvest Ransomware Attack: Stolen Data Now Publicly Disclosed appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.
State-Sponsored Hackers Weaponize ClickFix Tactic in Targeted Malware Campaigns
TGCTF Crypto-wp
Critical Erlang/OTP SSH Vulnerability Allow Hackers Execute Arbitrary Code Remotely
A major security flaw has been uncovered in the widely used Erlang/OTP SSH implementation, drawing urgent attention from the cybersecurity community worldwide. The vulnerability, tracked as CVE-2025-32433, exposes systems to unauthenticated remote code execution, potentially allowing hackers to fully compromise affected servers with ease. Overview of the vulnerability The vulnerability was discovered by a research team […]
The post Critical Erlang/OTP SSH Vulnerability Allow Hackers Execute Arbitrary Code Remotely appeared first on GBHackers Security | #1 Globally Trusted Cyber Security News Platform.
Artificial Intelligence – What's all the fuss?
CISA warns of increased breach risks following Oracle Cloud leak
How Critical Infrastructure Leaders Are Rethinking Cybersecurity
S4 EP 5: What’s changed, what’s working, and how to prepare for when, not if, incidents hit critical infrastructure.
The post How Critical Infrastructure Leaders Are Rethinking Cybersecurity appeared first on Security Boulevard.